Comments
Sort by recent activity
Hi Clare,
You aren't the first person to say this, we will look into adding an switch to SQL Compare that stops identical databases reporting as an error. Hopefully, we will be able to get it into the next version of SQL Compare.
Regards,
Jonathan / comments
Hi Clare,
You aren't the first person to say this, we will look into adding an switch to SQL Compare that stops identical databases reporting as an error. Hopefully, we will be able to get it into...
Mike,
Does this text
"ALTER TABLE #AdTbl (SellerAdID int, ItemID int, ProfileID int) "
actually exist within the database objects or the object script that you are comparing when you view the object in SSMS or does it say CREATE there?
If it says CREATE then can you post the creation SQL for the procs in both the databases?
Sorry to be so fussy,
Jonathan / comments
Mike,
Does this text
"ALTER TABLE #AdTbl (SellerAdID int, ItemID int, ProfileID int) "
actually exist within the database objects or the object script that you are comparing when you view the objec...
Hi Mike,
What you have reported is rather worrying as SQL Compare should not be able to alter the contents of procs. Can you double check that the procs don't contain ALTERs already? If you are still getting this issue please can you post an example of this, ASAP?
Many thanks,
Jonathan / comments
Hi Mike,
What you have reported is rather worrying as SQL Compare should not be able to alter the contents of procs. Can you double check that the procs don't contain ALTERs already? If you are s...
That is good news, you had me worried there for a day.
We don't think that we made SQL Compare 6 less tolerant to network issues, but if you could keep us posted about this that would be useful.
Thanks.
Regards,
Jonathan / comments
That is good news, you had me worried there for a day.
We don't think that we made SQL Compare 6 less tolerant to network issues, but if you could keep us posted about this that would be useful.
Th...
Just out of interest, how large is the database you are trying to compare. / comments
Just out of interest, how large is the database you are trying to compare.
Hi there,
We have a similar size database on out test systems here, and we don't have any problems with timeouts, so it is likely to be an object in your database that SQL Compare is processing is causing problems rather than the size of the database.
What is the last message displayed in the progress dialog before this error occurs?
Can you run a trace on the effected server whilst running SQL Compare? Then locate the last query in the trace that was run with an application name of "Red Gate Software - SQL Tools". If you could run this query in SSMS or QA and let us know the average execution time that too would be useful as would the trace itself.
Regards,
Jonathan / comments
Hi there,
We have a similar size database on out test systems here, and we don't have any problems with timeouts, so it is likely to be an object in your database that SQL Compare is processing is ...
Hi there,
No we didn't change this value, I will have a word with the developers and see if we had added something that might have caused this.
Is it happening all the time to all databases on this server?
Regards,
Jonathan / comments
Hi there,
No we didn't change this value, I will have a word with the developers and see if we had added something that might have caused this.
Is it happening all the time to all databases on this...
Hi there,
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 and the SQL Differences pane will highlight differences, when the top grid will report 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.
In the case that you highlight SQL Compare will display only report that the objects are different in the top grid if there is a different elsewhere in the objects. The ordering of triggers alone shouldn't cause the top grid to be report a difference. If it has then you have found an issue. If you can forward me the schema of the effected objects I will take a look and see what we can do about it.
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. Sorry.
Jonathan / comments
Hi there,
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 o...
Hi there,
This sounds like the SQL Differences pane matching has gone a bit wrong, if you can post an example or screen shot I will take a look at it.
We actually consider WITH NOCHECK a semantic difference and there is an Ignore WITH NOCHECK option on the Project Configuration > Options > More Options dialog to disable this behaviour.
Thanks,
Jonathan / comments
Hi there,
This sounds like the SQL Differences pane matching has gone a bit wrong, if you can post an example or screen shot I will take a look at it.
We actually consider WITH NOCHECK a semantic d...
Hi there,
With code lock off just days away and we cannot sanction putting major changes to functionality like this in place just right now. However, the amount of support that has been generated for this request since the beta has gone out has all but ensured that we will be implementing this option in the near future.
I am trying to have this feature scheduled for the first point release after the SQL Compare 6 release. Time scales are a bit vague at the moment, but it should be in there before the end of the summer.
Thanks,
Jonathan / comments
Hi there,
With code lock off just days away and we cannot sanction putting major changes to functionality like this in place just right now. However, the amount of support that has been generated ...