Updated: May 11, 2015
I’ve been giving this presentation for about 4 years now. It’s morphed, mutated, and improved incrementally for that entire time. I say I have a ‘top 10’ but it’s closer to 15 or so. It’s a VERY interactive session, with live demo. And there’s always lots of questions as we go.
But, if you’re not able to see this in person, I do have a slidedeck on slideshare – you can see that here:
Of course I recommend you go straight to the source, which would be the posts on this website. On the next to last slide, I have bookmarked the posts that go into more detail for each tip and trick.
Do you have a favorite tip or trick that I’m missing? Please share it here in the form of a comment. I’ll try to work it in for the ‘next release.’
I often present this content ‘live’ and in living color at local Oracle User Group conferences, but if you can’t make it to Open World or KScope or whatever, I offer this to you:
Would you like me to present to your company or organization?
We can setup a WebEx and phone session over about 60 minutes and cover the material that’s important to your organization. I frequently customize these sessions to fit your needs and requirements. And it’s free, of course 🙂
I’ve seen a couple of your webcasts and several people in my department use SQL Developer (versoin 3). It’s a great tool. We’re having an odd problem now, though. In some schemas we cannot copy tables via the right-click on the table, select Table>Copy. One person who’s tried this gets a table not found error. When I try it, nothing happens. I had a DBA review the security in the schema that doesn’t work and compare it to one that does work. Nothing jumps out as a potential cause. The user can create tables. Do you have any idea what the problem might be?
What happens if you take the generated script from the SQL panel on the pop-up and run that in the Worksheet or SQL*Plus?
Appreciate your support and hanging out at our webcasts. And thanks for reaching out with your issue. I’ll do my best to get it going for you!
One note, you’re now 2 versions behind (3.1, 3.2) – we might be looking at a bug that’s been fixed since v3.0.
Figured it out. It turns out it was a security issue. In order to copy a table in SQL Developer the user needs access to the ALL_USERS view. That was revoked from everyone this past year as part of security vulnerability remediation. Someone else ran into this, though, since the DBAs created a special role just for this. Once the user was granted the role, it worked.