When I script a database out to a file using SQLCompare it uses brackets around identifiers, e.g., [dbo].[StoredProcName]. However, when I compare this script to a live database, the live database is scripted without brackets. No match.
Comments
1 comment
-
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?
Add comment
Please sign in to leave a comment.