We are using the trial version V6.7.0.176 and we have encountered an issue with the generated script when we perform data compare between two databases.
If we select the “Drop/Create primary keys and unique constraints” option the generated script has only drop constraint statement for tables that are synchronized.
The issue is that they may exist other tables with foreign key constraint on the tables that the primary key constraint will be dropped and the drop of those constraints is not in the script because those tables have not been selected for synchronization.
So when we try to execute the script we are taking an error as below:
The constraint <PK_constraint> is being referenced by table <foreign_key_table>, foreign key constraint <foreign_key_contraint>.
Can you please advise if there is a workaround for that?
I ran a database compare in 8.1 and it crashed when I tried to generate the sql script that would make the target db the same as the src db. I didn’t bother to report anything. I will next time.
This is not the same error that was initially reported. However, I believe that I’ve seen this error myself. But I don’t remember what I did to resolve it. If you report it, tech support may be able to provide a solution for your error. Given the date of the initial report (first post) it appears that they’ve sat on this issue for nine years. It would be great if other users could put some pressure on tech support to get this corrected. In my opinion, the ability to compare and sync schema and/or data is a key feature of this tool.
I reported bugs in the past on this forum - some of them were fixed others not. Usually reporting these bugs takes time and context switch. If I were a developer working on this product, I would probably have a number of sql servers of different versions and databases with sql objects that cover pretty much all the types of objects that you can create. I would have a gazillion test cases that would cover all the script generators. I agree that it is not simple, it is very complex but some of the bugs I reported were simple.
I suspect - and this is a trend with other “software” companies - that Quest is not really a software company that innovates continuously and tries to keep their customers happy and stable by fixing bugs asap. They might have been bought by a hedge fund or whatever entity that tries to extract maximum revenue while doing minimal work. Maybe they don’t have a big enough customer base anymore to justify the spending.
Every time when I upgrade to a new version I always keep previous versions around. Historically, I was afraid of running new versions against production databases. My main version that I currently use is version 8. I just upgraded to version 8.1 to give it a try. I already posted an issue about it and I hear the crickets.
I suspect that your analysis is spot on. We’ve been a Quest customer for only a few years. But I’ve been a software developer for many years. I can remember when software had to work. I can remember when TOAD software products were innovative and helpful. Based on recent experiences with Quest and their products, I’m beginning to feel like their business model is a giant con game.
We need tools to help build databases and applications in a timely manner. I’m not sure where to turn for data modeling and related tools.
I’m beginning to feel like their business model is a giant con game.
100%
I’ve been looking for db tools for SQL Server and other dbs for a very long time. I currently use Jetbrains DataGrip for editing and sporadically I’ve been using Sql Prompt from RedGate as a plugin for SSMS (I dislike SSMS intensely).
Each of these tools have strong points and weaknesses. I use DataGrip more for editing sql scripts, and I use Toad to query data and to investigate issues. I would say Sql Prompt offers the best coding experience and the best code completion and the best code formatter, at least as far as I am concerned, everyone is different.
At one point I tried a tool from South Korea, called https://www.sqlgate.com/ . But I didn’t like and I stopped paying their subscription.
Unfortunately, Quest killed another product that I liked and was affordable, Toad Data Modeler.
Anyway, I think passionate people about databases create the best products, and, I don’t think Quest has an environment where developers feel incentivized and strive to create one of the best products.
We have a subscription for and I still use Toad Data Modeler. It has some minor issues. Quest tech support doesn't know the product. But I am able to use it to model databases and generate change scripts. We are probably going to have to find a replacement. Any suggestions for database modeling tools?
I just received a “hot fix” from Quest tech support for this problem. They are planning to fix it in the next release but if you need it now, contact them.
