Using the latest MS jars (1.1) and SQuirreL 2.6.8 logging into a SQL Server instance with a default database(catalog) on the URL, but where we have access to two other databases (catalogs) on the same instance, the tables for other databases do not show up in the object tree. Sometimes, if you change the catalog setting in the option box up top to one of the other databases and refresh the tree, the original database's tables disappear and the new database's tables appear.
I switched to the older MS jars, and it was a little better behaved: every time I switched settings in the catalog box, the tree self-refreshed and only tables in the selected database were visible. A lot of overhead user ids were missing from the object tree, which is nicer for most users.
Neither of these behaviors is optimally intuitive or facile. Caching overhead worries should not override good user interface. If the caching could be done in pieces as the tree is opened or objects are referenced, that might make it less of a bump, but the cache refresh runs very fast for me already. I'd like to see all the tables of all the schemas I have access to without fiddling with multiple controls. Am I missing a configuration setting for this to happen?
Sorry, forgot to log in.
This is with 1.6_11 JRE, and on a MS Windows 2000 PC.
I use a Solaris 10 SPARC system and the same version JAVA and jars, with the 1.1 MS jar I can never see quite accessable tables of other databases(catalogs) no matter what the catalog setting up top. With the older jar, it works as on the PC with this MS JDBC jar: tables appear when you select the right catalog above and it auto-refreshes, and disappear where the catalog is wrong even though they are still visible.
I tried 'use <db_name>' on the SQL window and I can always see tables only on my current database.
BTW, sometimes, when I change the catalog setting, I get:
Error: Could not locate entry in sysdatabases for database '"db_xxtestxx"'. No entry found with that name. Make sure that the name is entered correctly.
SQLState: S0001
ErrorCode: 911
I get the same lack of access to the other db in the object tree with the JTDS JARs and with the JDBC-ODBC Bridge on Windows. If I go to the sql window and "Use <db_name>" and go back to the tree and refresh it, I can only see the tables in <db_name>, so I must jump back and forth (or open two sessions) to get info for write a query joining the two DBs' tables.
dgpickett,
Try the latest snapshot and let us know if the "Error: Could not locate entry in sysdatabases for database" problem is fixed for you.
Rob
Yes, the Snapshot 20090107 switches between DB based on the combo box without error, now.
This lets us see one at at time, which is better but still a bit lame. It should just select the right db when you click that subtree, and not flush out the cache/display of the last db. It'd be nice to be able to open two databases' dbo table lists at once.