Comments
Sort by recent activity
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...
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...
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...
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...
The projects are real work, so I can't share them. When I have unchecked an object from an object change list, to exclude the object from generate and import, what, precisely, in the project, retains the knowledge that I have excluded the object? Is there a cache or config file somewhere that I could examine? Maybe I could see differences between the project settings wherever they are saved. / comments
The projects are real work, so I can't share them. When I have unchecked an object from an object change list, to exclude the object from generate and import, what, precisely, in the project, retai...