How can we help you today? How can we help you today?
JonathanWatts
Good news then, this is being "considered" for the next version of SQL Refactor. As it is a fairly popular request it has a good chance of making it, as long as it is technically possible to do this inside of SSMS. Regards, Jonathan / comments
Good news then, this is being "considered" for the next version of SQL Refactor. As it is a fairly popular request it has a good chance of making it, as long as it is technically possible to do t...
0 votes
Hi Gary, Sorry to hear that you experiences with SQL Compare 5 haven't been as one would have hoped. I will try to address your points as best I can, but can I ask which version of SQL Compare you were using before v5? 1) If you cannot see a different then it probably is in a line ending, can you check that your line endings are identical. This issue (66330) is marked down for addressing in a future version of SQL Compare. 2) There is an Ignore "SET QUOTED_IDENITIFER and SET ANSI NULLS" option in the Project Configuration > Options > More Options dialog which should give you what you need here. 3) I completely agree with you that this is a bug (68764) and a very idiotic one at that :oops:. We will be addressing it in future versions of the product. Hopefully, the first point release. 4) Because SQL Compare used the object definitions straight from the SQL Server system catalogs then I think that we would always consider this a difference the names are different therefore the object is different. 5) The problem you are seeing is because of the two ways that SQL Compare compares objects. At the start of the comparison, or each time you refresh, the engine does a semantic comparison of all the objects in the data sources and stores these results in the top grid. However, each time you select an object in the top grid the SQL Differences pane does a simple textual comparison of objects. This is done to improve performance and memory usage, and because 90% of textual differences are actually semantic differences too. However, in some cases like the one you highlight, a textual difference isn't actually a semantic difference as extra brackets don't change the result of the default. But the SQL Differences pane will highlight the textual differences although the top grid reports the object as identical. As we display most of these objects exactly as they are stored in the system catalogs we don't feel that we should alter them, and some of these differences may actually be of interest to users. The extra brackets that SQL Server 2005 adds shouldn't cause the top grid to be report a difference if that is the only difference in the object. This behaviour does cause a fair amount of confusion when looking at results so we are going to have to look into improving the SQL Differences pane difference matching in future releases, but this won't be changed in the initial point release of version 6. 6) There is also an ignore "Identity seed and increment values" in the same location as the option in (2) that should help. 7) This will be hopefully addressed in SQL Compare 6.1 If you have any further queries, you can contact me in this tread or via email (below). Regards, Jonathan : / comments
Hi Gary, Sorry to hear that you experiences with SQL Compare 5 haven't been as one would have hoped. I will try to address your points as best I can, but can I ask which version of SQL Compare you...
0 votes
Mike, We found a race condition in SQL Compare which could be causing this hanging. We think we have now fixed this, so this should no longer occur when the final release comes out. Regards, Jonathan / comments
Mike, We found a race condition in SQL Compare which could be causing this hanging. We think we have now fixed this, so this should no longer occur when the final release comes out. Regards, Jonathan
0 votes