Comments
3 comments
-
Thanks for your post.
SQL Compare will only successfully compare SQL Scripts that were created by SQL Compare.
I believe SQL Compare is expecting to find the CREATE CERTIFICATE statements in their own file, and finding them as part of another object is causing the parsing error. -
Each certificate is defined in its own file, not as part of another object.
The files reside in subdirectories like \Schema Objects\Database Level Objects\Security\Symmetric Keys,
\Schema Objects\Database Level Objects\Security\Certificates, and \Schema Objects\Database Level Objects\Security\Master Keys. The example cites the entire contents of one such file.
Other files for database roles are successfully parsed from \Schema Objects\Database Level Objects\Security\Roles\Database Roles. All other SQL objects have their defining files in a directory structure under \Schema Objects\Schemas\dbo. -
Were the scripts created by SQL Compare?
Add comment
Please sign in to leave a comment.
SQL Compare 9 (v9.0.0.79) complains about each file which includes a CREATE CERTIFICATE, CREATE SYMMETRIC KEY, or CREATE MASTER KEY command. The issue cited by SQL Compare is "Non-schema statement was ignored."
Each of these files parses correctly within SSMS.
An example:
Is this a bug?