Comments
Sort by recent activity
Sorry, it is not currently possible to define custom file endings for scripts. We've had a couple of requests for this feature and we'll consider implementing it in future, but as SQL Compare currently uses the file endings to determine which files in a folder to read and which to ignore, this is actually more difficult than it looks. / comments
Sorry, it is not currently possible to define custom file endings for scripts. We've had a couple of requests for this feature and we'll consider implementing it in future, but as SQL Compare curre...
If you've just created it with writeToFolder then you should be able to use the following:
db.Register(path, null, options);
where 'db' is a fresh Database object, path is a string which contains the path to the folder, and options is an Options with whatever option set you want to use for registration.
The 'null' is where you would put a ReadFromScriptDatabaseInformation object if you didn't have a SqlCompareDatabaseInfo.xml file in the directory, but as you've just written it out you ought to have one already there with settings in. (If you want to set things like the database version yourself, or there isn't an xml file in the directory, pass in a ReadFromScriptDatabaseInformation object - you can just construct them with the empty constructor and then set the fields manually.) / comments
If you've just created it with writeToFolder then you should be able to use the following:
db.Register(path, null, options);
where 'db' is a fresh Database object, path is a string which contains t...
If you have a 'textual object' (i.e. an object for which SQL Server stores the actual text of the object as provided when it was created - e.g. views, stored procedures, functions) with 2005 syntax in it, SQL Compare doesn't change the contents of the object even when attempting to synchronize it to a different version of SQL Server.
Whilst we could attempt to parse textual objects and work out what to change between versions, it would be a lot of work and we haven't yet had adequate demand for this feature to consider implementing it. I'll raise this as a feature request and note that it has been mentioned on the forums, but it is unlikely to be implemented unless more people mention it as a problem, due to the large amount of work it would entail. / comments
If you have a 'textual object' (i.e. an object for which SQL Server stores the actual text of the object as provided when it was created - e.g. views, stored procedures, functions) with 2005 syntax...
I've added a reference to this thread to the feature request for better error messages on reading inconsistant scripts. Thank you for your report. / comments
I've added a reference to this thread to the feature request for better error messages on reading inconsistant scripts. Thank you for your report.
The most common cause of that error is that one of the scripts (not necessarily the one it claims to have finished reading on) has a foreign key that refers to a non-existent table. (Other dependencies with a missing target object may also cause this error, like a view referring to a non-existent table.)
If there's nothing obviously wrong of this nature, or you are reading scripts that were generated by Compare in the first place, tell me and I'll investigate further. / comments
The most common cause of that error is that one of the scripts (not necessarily the one it claims to have finished reading on) has a foreign key that refers to a non-existent table. (Other dependen...
Sorry, I misread your original post - with a CLR stored procedure, SQL Compare does appear to be misreading the Execute As clause. Thank you very much for reporting this - hopefully we can get it fixed for the upcoming point release. / comments
Sorry, I misread your original post - with a CLR stored procedure, SQL Compare does appear to be misreading the Execute As clause. Thank you very much for reporting this - hopefully we can get it f...
This is not intentional - SQL Compare should distinguish EXECUTE AS OWNER from EXECUTE AS CALLER. It appears to do so succesfully in the test database I have here (very simple stored procedures decorated with different EXECUTE AS statements), in both 5.3 and the current version 6.
If you could give us some more details (ideally, a database backup of the troublesome database, or at least the script of the stored procedures causing the problem) I might be able to reproduce the problem and then we will work on fixing it, but I understand that handing out that kind of information isn't always possible.
My email address is michelle.taylor@red-gate.com if you want to send more details privately. / comments
This is not intentional - SQL Compare should distinguish EXECUTE AS OWNER from EXECUTE AS CALLER. It appears to do so succesfully in the test database I have here (very simple stored procedures dec...
Once you have compared your databases, Compare will display all of the objects in your databases in a grid. In the middle of each row (there is one row per object) will either be an equal sign (if Compare thinks the objects are equal) or a check box (if Compare thinks they are different). If you don't want to synchronize a particular object, uncheck its check box before synchronizing. / comments
Once you have compared your databases, Compare will display all of the objects in your databases in a grid. In the middle of each row (there is one row per object) will either be an equal sign (if ...
The easiest way to create and maintain SQL script files and faithfully recreate a database schema with them is to maintain individual object script files and use SQL Compare 6 to synchronize them up to the live database. SQL Compare 6 will take care of getting the dependancies in the right order on synchronization to a live database.
If you want the actual script which creates all the objects in the correct order, just compare the script files with an empty live database and save the resulting synchronization script. / comments
The easiest way to create and maintain SQL script files and faithfully recreate a database schema with them is to maintain individual object script files and use SQL Compare 6 to synchronize them u...
This bug is fixed in the currently released version of Compare (6.2) - there is now an /allowIdenticalDatabases option (alias: /aid) for the command line which will produce a report instead of an error for identical databases. / comments
This bug is fixed in the currently released version of Compare (6.2) - there is now an /allowIdenticalDatabases option (alias: /aid) for the command line which will produce a report instead of an e...