Cannot reverse engineer Azure SQL dababase after updating DBSchema

DbSchema Issues
Post Reply
DbSchemaUser
Posts: 2
Joined: Mon Oct 09, 2017 8:08 am

Cannot reverse engineer Azure SQL dababase after updating DBSchema

Post by DbSchemaUser » Mon Oct 09, 2017 8:17 am

Updated DBSchema to version 7.6.3 build 4832.

Now we need to specify a URL pattern before being able to connect. Specified this:
jdbc:sqlserver://<host>;

Connecting to the Azure SQL DB, I can see and select my schema. Choosing the master DB works fine. Any other DB schema trigger an exception as soon as I try to do anything in the tree structure that lets you select what to include in the reverse engineering process (for example just unfolding the dbo node to see the subnodes (tables, triggers, etc.).

"com.microsoft.sqlserver.jdbc.SQLServerException: USE statement is not supported to switch between databases. Use a new connection to connect to a different database."

DbSchemaUser
Posts: 2
Joined: Mon Oct 09, 2017 8:08 am

Re: Cannot reverse engineer Azure SQL dababase after updating DBSchema

Post by DbSchemaUser » Mon Oct 16, 2017 7:42 am

Need to know of this is a user error (and some indication of what the solution may be), or if it is a known bug that is being looked at.

DbSchema is useless to me, if I cannot reverse engineer my database.

Post Reply