Comments
Sort by recent activity
Which Refresh do you mean? Refresh Comparison, the refresh option on the server list and the refresh option on the database list all seem to be working fine for me.
If nothing has changed in the databases then Compare will often return very quickly from Refresh Comparison - if you have the 'Close message box on completion' box checked on the comparison progress dialog then the progress dialog may not display at all. / comments
Which Refresh do you mean? Refresh Comparison, the refresh option on the server list and the refresh option on the database list all seem to be working fine for me.
If nothing has changed in the da...
The script you've provided there is the script that Compare generates when it hasn't actually generated any actions to synchronize between databases, so this does look like a bug (Compare shouldn't produce just that script because if it's producing a synchronization script it should be generating some actions).
I've just tried out saving some tables with extended properties on to snapshots and scripts, and comparing the results to each other, and it's working fine for me. Can you give me more information about the tables and extended properties? You can email more information to michelle.taylor@red-gate.com if you don't want to post it on a public forum.
(What would be most useful is a copy of the full creation script for those two tables, but other useful information would be whether the extended properties are directly on the table or on a column, constraint, index or trigger, what data type the value of the extended properties has, and anything interesting about the table like computed columns or complex constraints or triggers - it might be that the problem is in fact with another element of the table, but the SQL Difference pane's textual comparison is getting confused amongst the extended properties instead of reporting the real problem.) / comments
The script you've provided there is the script that Compare generates when it hasn't actually generated any actions to synchronize between databases, so this does look like a bug (Compare shouldn't...
I couldn't find a previous report in the bug database for this issue, so I've raised it with the developers. I'm not certain that it will be fixed for the initial 6.0 release as our schedule is quite tight, but rest assured that it is now in the queue and will get looked at for this release and for any subsequant point releases if we don't manage to fix it in time for the major release. / comments
I couldn't find a previous report in the bug database for this issue, so I've raised it with the developers. I'm not certain that it will be fixed for the initial 6.0 release as our schedule is qui...
The problem that you're encountering is that the beta version of Compare doesn't have a populated 'Encoding' dropdown for saving the SQL script, and is defaulting to saving it as UTF-8 With Preamble. The three characters you see at the start of the script are the preamble.
If you load up the script with Management Studio, it understands the syntax and the characters do not appear, but if you load it up with Query Analyser, QA doesn't understand that it's UTF-8 With Preamble and just shows you the characters.
In the final release version, there will be a drop-down menu in this save dialog so that you can choose Unicode or ASCII format, which QA will recognise and open correctly. / comments
The problem that you're encountering is that the beta version of Compare doesn't have a populated 'Encoding' dropdown for saving the SQL script, and is defaulting to saving it as UTF-8 With Preambl...
It doesn't look (from Books Online) like you can create a DEFAULT constraint as a table constraint within a CREATE TABLE statement - if you've managed to do this, could I have some example SQL, please? [image]
The release version of Compare 6 will be able to read in defaults created with ALTER TABLE, but may still have some issues around using scripts with this syntax as the target database in a synchronization. / comments
It doesn't look (from Books Online) like you can create a DEFAULT constraint as a table constraint within a CREATE TABLE statement - if you've managed to do this, could I have some example SQL, ple...
The exception that you're getting off the scripts you've provided is caused by the foreign key FK_AccessControlList_SecurityDescriptor in the table AccessControlList, which points to a table SecurityDescriptor which isn't in either file. Unfortunately it's quite difficult to track down all the individual permutations of problems like this, so some of them still don't have particularly nice error messages when Compare encounters them.
Having taken out the foreign key, I can see the problem you're reporting - the ALTER TABLE ADD CONSTRAINT DEFAULT statement doesn't appear to be read in from the script at all. Thanks for spotting this - I've reported it to the developers and it will probably be fixed for the final release (and for the point release if not). / comments
The exception that you're getting off the scripts you've provided is caused by the foreign key FK_AccessControlList_SecurityDescriptor in the table AccessControlList, which points to a table Securi...
Constraints added inline (i.e. in a table) ought to be recognised as identical to constraints added via ALTER TABLE.
There are a couple of things that might be causing them to look different:
1) The constraints will come up as different in the Difference Viewer pane at the bottom of the comparison window, because that just does a textual comparison (for speed reasons) rather than a full semantic comparison. The comparison determining whether the objects are marked as different in the main comparison window is much more sophisticated than the one run by the difference viewer. So if you have any other differences on that table, that might be the cause.
2) If either of the constraints are not given a name in the script, Compare will generate a random name for them in the same way that SQL Server would, but it is quite likely that it will generate different names for the two different constraints. Turning on the option 'Ignore Constraint and Index Names' or naming the constraints explicitly in the scripts will stop this showing up as a difference. (Unfortunately it is impossible to guess what name SQL Server will give an unnamed constraint before the script is run into a live database... it will be different if you run the script into the same live database twice.)
If it is neither of these, you may have succesfully found a bug :oops: and we'd like some more details on what these constraints look like so we can reproduce it... / comments
Constraints added inline (i.e. in a table) ought to be recognised as identical to constraints added via ALTER TABLE.
There are a couple of things that might be causing them to look different:
1) Th...
If you just want to run the scripts / certain objects from the scripts into a database, you probably want to use Compare to synchronize the script folder into the database. (If you want to do this in an unattended fashion, the command line is the correct way to do it.) / comments
If you just want to run the scripts / certain objects from the scripts into a database, you probably want to use Compare to synchronize the script folder into the database. (If you want to do this ...
The release version of Compare 6 will definitely support reading a directory structure recursively for script files, rather than just reading a flat single directory as the Beta version does. / comments
The release version of Compare 6 will definitely support reading a directory structure recursively for script files, rather than just reading a flat single directory as the Beta version does.
We've added comparison of permissions on system schemas, and comparison of other system objects is still on the list. / comments
We've added comparison of permissions on system schemas, and comparison of other system objects is still on the list.