Activity overview
Latest activity by tee
We have only 1 build agent and all of the release agents are the same version. I don't imagine this is related to the agents since the 1st release executes successfully. Cause of the release failure - error message: System.Management.Automation.CmdletInvocationException: An unhandled error occurred: RedGate.SQLCompare.Engine.Registration.ReadFromSnapshot.UnsupportedSnapshotException: The database snapshot was saved by a newer version of SQL Compare The scenario:
The 1st release executes the entire build, making changes on the target server as expected, (no errors), and installs the __MigrationLog] and [__SchemaSnapshot] tables, including populating the [__SchemaSnapshot] table with a record (records GUID matches in all target databases)
Subsequent releases fail, citing the above error [__SchemaSnapshot] table in the target database(s)
There are no records in either the development or shadow database's [__SchemaSnapshot]'s table
In summary, the error message and failure only occur in subsequent releases (never in the first). Since every successful release inserts a record into the [__SchemaSnapshot] table, I attempted to resolve the issue by adding the truncate statement to the the post - deployment script. I also tried adding to the pre-deployment script. Neither method removes the record(s). In order for the release to execute (except for the 1st release) I must manually delete the [__SchemaSnapshot] record from each targeted database. Question: How can I automate the truncation of the [__SchemaSnapshot] table, on target databases, from a script within project?
/ comments
We have only 1 build agent and all of the release agents are the same version. I don't imagine this is related to the agents since the 1st release executes successfully. Cause of the release failur...
SQL Change Automation adding permission assignments in the view script and creating schema for role
The project includes a filter that excludes users, roles and security policies. But the baseline script is including object permission assignments to users and roles. I edited the baseline (note th...
baseline includes permission statements with all users and roles excluded
The project Filter is set to exclude all users and roles, (unchecked User and Role and Security Policy items' check boxes in the Filter list). SQL Compare 14 was used to create the filter. Role, Us...
Thank you for the information on the synonym. I'm not sure if it will prevail but it's worth looking into. I am excluding the views via a filter for testing the pipeline but I won't be able to filter out these objects in the production project. Appreciate your knowledge share. / comments
Thank you for the information on the synonym. I'm not sure if it will prevail but it's worth looking into. I am excluding the views via a filter for testing the pipeline but I won't be able to filt...
Is there anyway to ignore code that references linked servers?
Is there an option to ignore linked server errors on the project server. I have objects that reference a linked server from code but will never add new code that uses the linked server, so I don't ...
SQL Change Automation - error during release
Wondering if the cause of the error, below, is explainable with the information provided (below) or if the cause is already known:error = "RedGate.SQLCompare.Engine.Registration.ReadFromSnapshot.U...
Update: In answer to your question, the error occurred with any database, local or network/remote - unable to create a project, or open a project. Resolve: I uninstalled SQL Server Management Studio 18.3.1 and installed SQL Server Management Studio 18.2 and SCA seems to working properly in that previous version. / comments
Update: In answer to your question, the error occurred with any database, local or network/remote - unable to create a project, or open a project. Resolve: I uninstalled SQL Server Management Stud...
consider adding feedback to the sql change automation '<-] Import and generate scripts' link
Also, I have a very minor request - in the next update/release please consider adding an distinguishable background color behind the "<-]Import and generate scripts" hyperlink/button to give develo...
SQL Change Automation not showing up in SSMS 2014 and not working in SSMS v 18.3
=======================================UPDATE===========================================This issue was resolved by uninstalled SSMS v. 18.3 and installing v 18.2 instead.===========================...
Thank you. I understand, from your reply, that 4.0 is backwards compatible.Am I understanding you correctly 'that after installing the shell scripts on the build and release server(s) that there is never a need to upgrade the shell scripts on the server(s)'? / comments
Thank you. I understand, from your reply, that 4.0 is backwards compatible.Am I understanding you correctly 'that after installing the shell scripts on the build and release server(s) that there is...