So I’ve been having this bug lately with Oracle SQL Developer…

It started because the SQL Studio that comes with SQL Server 2005 *blows*.  It appears to be written in managed code, is a memory hog, and is slow as frozen dog shit.  So, given that I had been doing some oracle stuff and had SQL Developer sitting on my system, I decided to use that.  For awhile, all was good, and right with the world.

Then some ass in IT decided to move all of our dev databases from servername to servername\servername2005.  I tried to go in and reconfigure my servers in SQL Developer only to find that there was no way to specify the instance name for SQL Server connections using the jtds driver.

I googled this, and found a workaround which was to use 1433;instance=instancename in the port box.  This allowed me to connect, but most of the tables were missing.  So I went back to using SQL server’s shitty utility to get my work done.

I fired up SQL Developer again today to get some oracle work done and it had an update for the jtds driver, so I decided to give it a try again.  Still nothing, but I was renewed in my search for a solution.  I finally found one…instead of 1433;instance=instancename in the port box, I used 1433/databasename;instance=instancename in there.  Now all my tables show up just fine.

Sanity once again restored.