| bio | website | sqlfiddle.com |
|---|---|---|
| location | Vancouver, WA | |
| age | 31 | |
| visits | member for | 1 year, 5 months |
| seen | Apr 15 at 13:09 | |
| stats | profile views | 47 |
Web Developer (strengths in ColdFusion, SQL, jQuery)
twitter - @sqlfiddle
Developer of http://sqlfiddle.com
|
Mar 12 |
comment |
Interpreting SQL Server's Showplan XML Justin - I cannot sing your praises high enough! Your code was super easy to integrate (a match made in heaven!), and just amazing results (as you can see). It's pretty rare that there is something out there that really is the perfect solution to a problem, but this was. Thanks so much! |
|
Mar 12 |
accepted | Interpreting SQL Server's Showplan XML |
|
Mar 11 |
revised |
Interpreting SQL Server's Showplan XML added 574 characters in body |
|
Mar 9 |
comment |
Interpreting SQL Server's Showplan XML @JNK - I've thought about that, but according to the MS docs (msdn.microsoft.com/en-us/library/ms180765.aspx) that option is deprecated. I figured I should go with the most preferred option. I suspected (and now see confirmed) that the XML option would afford more flexibility via manipulation, as well. |
|
Mar 9 |
comment |
Interpreting SQL Server's Showplan XML Wow @MartinSmith that's exactly what I'm after. Thanks a lot! If you want to put that down as an answer, I'll happily upvote and accept. |
|
Mar 9 |
awarded | Commentator |
|
Mar 9 |
comment |
Interpreting SQL Server's Showplan XML @MartinSmith - by "seen one" do you mean seen a visual representation of the showplan xml? If so, see my update. |
|
Mar 9 |
revised |
Interpreting SQL Server's Showplan XML New option |
|
Mar 9 |
asked | Interpreting SQL Server's Showplan XML |
|
Feb 8 |
awarded | Student |
|
Feb 8 |
comment |
Trouble killing sessions then immediately dropping users in Oracle 11g XE Thanks again Justin! DISCONNECT ... IMMEDIATE appears to work great! See my updated question text with the final script. |
|
Feb 8 |
accepted | Trouble killing sessions then immediately dropping users in Oracle 11g XE |
|
Feb 8 |
revised |
Trouble killing sessions then immediately dropping users in Oracle 11g XE added 948 characters in body |
|
Feb 8 |
comment |
Trouble killing sessions then immediately dropping users in Oracle 11g XE Actually, having PMON wake more frequently sounds great to me. Remember, this is not a traditional environment for Oracle. My setup involves quickly building up and tearing down lots of "playground" databases. That is the whole use of this environment, so things that are normally a bad idea in real environments may not necessarily be so in mine. How would I adjust the PMON? BTW, I'm comparing all of this to the same types of tasks in MySQL, MSSQL, and PGSQL, and none of them have such an issue with killing sessions quickly. |
|
Feb 8 |
comment |
Trouble killing sessions then immediately dropping users in Oracle 11g XE BTW Justin - you're right, this is a strange problem to need to solve. You helped me answer another "strange" Oracle question on SO yesterday, so you may be wondering just what I'm up to. Well, I've built a site - sqlfiddle.com - that allows anyone to define their own databases and write their own queries, and then share that with others. One of the options for the backend is Oracle. You might even find this site useful for answering StackOverflow questions. |
|
Feb 8 |
comment |
Trouble killing sessions then immediately dropping users in Oracle 11g XE This works! Thanks, it is what I was looking for. Although, one thing still baffles me - why does it take SO LONG for the session to drop? I don't have any huge transactions pending, there is nothing at all happening, and yet it still takes upwards of 20-30 seconds before it finally dies and I can perform the drop. Ideas? If there is some system-wide setting I can adjust to fix this, that would be great too. |
|
Feb 8 |
comment |
Trouble killing sessions then immediately dropping users in Oracle 11g XE Thanks for your advice, but I'm still getting the error. Please see updated answer. |
|
Feb 8 |
revised |
Trouble killing sessions then immediately dropping users in Oracle 11g XE added 804 characters in body |
|
Feb 8 |
awarded | Editor |
|
Feb 8 |
revised |
Trouble killing sessions then immediately dropping users in Oracle 11g XE deleted 6 characters in body |