So this tip requires you upgrade to version 4.0.3 of Oracle SQL Developer – more on that in a second.
Version 4.0.3 is 95% bug fixes.
One of those bugs was submitted by my fellow product manager, Maria Colgan. Perhaps you know her on Twitter as…
Anyways, she is going to be using our favorite tool to help teach you how to use the new 184.108.40.206 database feature known as ‘In-Memory.’
What if you could get answers instantaneously—in seconds, not in hours or days?
Pretty amazing stuff. But, you probably want to see how it’s working, or even IF it’s working. Autotrace and a new optimizer hint makes that pretty easy.
You can turn it on and off between SQL statements for a table or whatever. If you capture these executions with AutoTrace and do a compare, you can see something like this:
- Autotrace query
- Pin results
- Autotrace 2nd query
- Pin Results
- Right-click on Autotrace results panel 1, and say ‘Compare…with 2’
You could of course do this in earlier versions of the tool, but the compare feature didn’t take into account the zero-level stats. They were removed before doing the compare…anyways the Autotrace compare works much better now.
And about that In-Memory Stuff
Maria holding MULTIPLE Hands-On Labs the week of Open World 2014. You’ll want to go into your schedule builder and sign up quickly before they’re all sold out!
> Version 4.0.3 is 95% bug fixes.
…but it still doesn’t carry window layout or enabled/disabled features or font size from previous install. Also, regular expression replace with captured groups still broken? Come on, it’s the key feature for any advanced editor! *grmblgrmbl*
Well, I guess that’s what I get for using bleeding edge with frequent updates, eh. Ranting aside, I like your tool, and it’s good that Sqldev moves forward, though it’s kinda sad Oracle doesn’t allow you to say anything about release dates or have a separate open public issue tracker. I’d feel silly posting all those minor bugs and enhancement requests I have in mind as separate MOS tickets, and they are likely to get ignored and archived both at OTN forums and Exchange…
Bugs shouldn’t be logged here or with on the Forums. They should be logged separately with MOS. They are publicly searchable if you have a MOS account. We’re not allowed by law to talk about release dates.
Give me bug #’s for the window layout issue and font stuff and I’ll look into them.
For this release, we only fixed a small number of bugs. I’ve seen many dozens of bug fixes implemented in the next release, which will be labeled 4.1.
>Give me bug #’s for the window layout issue and font stuff and I’ll look into them.
I posted it as a discussion to OTN forum (topic 3556319), not MOS. I have an account with access to MOS, but I felt uneasy to use it without permission, because I would write under my company’s name, in a sense. All the more so because I would open SR for SQL Developer bug, not for the Oracle database problems; using paid support on a Database to submit bugs on a free development tool sounded like a misuse, and I’m pretty sure I’m not the only one who feels like that.
I discussed it with my boss and got an OK, though, so I’ll just post SRs there from now on, I guess.
SQL Developer is included with your database license – it’s actually part of the database install. Absolutely no reason to feel guilty/silly submitting SRs on our development tools.
Ok, got it.
While I’m at it, I have another question – there’s a certain bug that annoys me since 4.0.0 (https://community.oracle.com/thread/2616015), and back then you said it’s still an open bug – can it be found in MOS, or did you mean an internal tracker?