User profile for Michelle T

SQL Compare seems to be preserving the current bracketing / qualification situation for each stored procedure when synchronizing to script. The name of the file will have brackets around the name (although the final release will not have these brackets as many users thought this was unnecessary and ugly in file names) but inside the script file the bracketing status should be preserved and compare back as identical. Do you have a particular example in mind where Compare puts square brackets around the actual name of the procedure in the CREATE PROC statement? A simple stored procedure created with CREATE PROC dbo.StoredProcName retains its lack of square brackets in the CREATE PROC statement for me. Or do you mean identifiers which are contained within some other object, rather than ones used to identify a procedure in the first line of the CREATE PROC statement? / comments

SQL Compare seems to be preserving the current bracketing / qualification situation for each stored procedure when synchronizing to script. The name of the file will have brackets around the name (...

0 votes

Did, at some point, one of your scripts get compared with its version set to 2005? You can set a 2000-sourced script's version to 2005, and this will produce schemas from the users in the manner you describe. If you have synchronized to a script while it is set to 2005 mode, then SQL Compare may have generated actual CREATE SCHEMA statements, which you will have to remove by hand. Otherwise, you can fix the problem by ensuring that the script is set to 2000 mode (you can set this in the projects individually, and if new projects with the script keep returning to 2005, you can manually set the default version for the script folder by editing the SqlCompareDatabaseInfo.xml file - DatabaseVersion is 9 for 2005 and 8 for 2000). / comments

Did, at some point, one of your scripts get compared with its version set to 2005? You can set a 2000-sourced script's version to 2005, and this will produce schemas from the users in the manner yo...

0 votes

I can't reproduce your problem here - whenever Compare creates or alters a stored procedure in a script database for me, I always end up with a CREATE PROC or CREATE PROCEDURE statement, never an ALTER PROC or ALTER PROCEDURE statement. The only way I could get ALTER PROC statements out of it was to compare to a snapshot or live database and save the script from there. Do you mean that the scripts were coming out with ALTER PROC statements (no CREATE PROC statements), or do you have stored procedures with CREATE statements in which are being changed, or do you mean that Compare scripts out CREATE PROC statements as if they were ALTER PROC statements which occasionally introduces differences? Also, note that SQL Compare can't reliably reproduce what SQL Server does to whitespace in stored procedures, so if you have turned the option Ignore Whitespace off, you might notice spurious differences in your stored procedures. If you're still having the problem with Ignore Whitespace turned on, we'd appreciate a 'before' and 'after' of the affected stored procedures (or a sample case that demonstrates the problem if you can't share the originals with us). You can email them to michelle.taylor@red-gate.com if you're willing. Regarding the defaults, SQL Compare does not consider the parentheses to amount to a difference which is show in the top pane (if your table is showing different then there is most likely some other difference in it - if there isn't, we'd like to know). The SQL Differences pane only does a textual comparison (for speed reasons) and hence shows up the parentheses as a difference even though the main comparison does not consider them as such. (SQL Compare can't reliably reproduce the bracketing of defaults and similar because their appearence in the live database depends on a range of factors we don't have access to, like whether the database was originally a 2000 database.) / comments

I can't reproduce your problem here - whenever Compare creates or alters a stored procedure in a script database for me, I always end up with a CREATE PROC or CREATE PROCEDURE statement, never an A...

0 votes

Thanks for that - you're correct, SQL Compare doesn't register this difference. I've raised an issue in our bug tracking system for this. (Unless it turns out to be very trivial to fix, I doubt it will be fixed in the 6.0 release, as code freeze is very close now - but it will be considered for the point release.) / comments

Thanks for that - you're correct, SQL Compare doesn't register this difference. I've raised an issue in our bug tracking system for this. (Unless it turns out to be very trivial to fix, I doubt it ...

0 votes

There's a project option, 'Ignore Statistics', that you can get to via the 'More Options...' button on the Options tab in the dialog you use to set up the connection to the databases you're comparing (headed 'Project Configuration'). / comments

There's a project option, 'Ignore Statistics', that you can get to via the 'More Options...' button on the Options tab in the dialog you use to set up the connection to the databases you're compari...

0 votes

Do you need to synchronize any permissions in this synchronization that you're performing? If not, then you might want to look at the Ignore Permissions option - if the only problem with synchronizing all the functions is that the permissions are changed to the wrong values, putting on Ignore Permissions would prevent SQL Compare from synchronizing the permissions on the functions. / comments

Do you need to synchronize any permissions in this synchronization that you're performing? If not, then you might want to look at the Ignore Permissions option - if the only problem with synchroniz...

0 votes

I've been attempting to reproduce this problem, but I'm not exactly sure what you mean by the syntax 'dbo.C.items' - if I attempt to use that syntax exactly in my view (with a different database name instead of C) SQL Server claims it can't find the object. If I use the syntax C..items then SQL Compare synchronizes the view correctly. If you could send me the actual view that's failing to synchronize (or preferably the schema for the whole database which it is in, as it might be something else in the database making the view fail to synchronize) to michelle.taylor@red-gate.com that would be very helpful. / comments

I've been attempting to reproduce this problem, but I'm not exactly sure what you mean by the syntax 'dbo.C.items' - if I attempt to use that syntax exactly in my view (with a different database na...

0 votes

I've done some testing with stored procedures that are entirely commented out, and they save out with the comments in and compare back to the original database with no differences. What style is your code commented out in? (I've tried a variety of commenting styles, but I might just not have got the one you're using.) If you could send the relevant procedures to michelle.taylor@red-gate.com that would be very helpful. / comments

I've done some testing with stored procedures that are entirely commented out, and they save out with the comments in and compare back to the original database with no differences. What style is yo...

0 votes

This error message doesn't necessarily mean you're trying to connect to a 2005 server - it just offers some troubleshooting information that might be useful if you were trying to connect to a 2005 server. In fact, the error message has no idea what the target server version is, because it hasn't managed to find the server at all. The most likely cause of this is that the network connection is not working, or the IP address is incorrect, or the server is not running. The server might also have had remote access turned off (while remote access is enabled by default on 2000 it is possible to turn it off). / comments

This error message doesn't necessarily mean you're trying to connect to a 2005 server - it just offers some troubleshooting information that might be useful if you were trying to connect to a 2005 ...

0 votes

Thanks for spotting that - I've put it on the bug list. I'm not certain it will be fixed, but we're now aware of the change. Note that you can get between the two sides of this dialog fairly quickly by pressing the 'tab' key repeatedly, no mousing required. / comments

Thanks for spotting that - I've put it on the bug list. I'm not certain it will be fixed, but we're now aware of the change. Note that you can get between the two sides of this dialog fairly quickl...

0 votes

How can we help you today?

Michelle T

Comments