The database snapshot was saved by a newer version of SQL Compare
GurpreetGill
Posts: 26 Bronze 1
Hi
We are using RG Azure DevOps extension ( build and Release) to do the deployments to SQL Server.
Everything was working well, but suddenly today start getting deployment error as
We are using RG Azure DevOps extension ( build and Release) to do the deployments to SQL Server.
Everything was working well, but suddenly today start getting deployment error as
"The database snapshot was saved by a newer version of SQL Compare"
We are not using SQL Compare any where, but just use SQL Change Automation only.
Any pointer to look into?
Thanks
Gill
We are not using SQL Compare any where, but just use SQL Change Automation only.
Any pointer to look into?
Thanks
Gill
Tagged:
Answers
SQL Change Automation uses SQL Compare internally so that's why you saw this message.
I think I reproduced your issue and there was a problem trying to update SQL Change Automation from the Powershell Gallery. We've release a new version of the Azure DevOps extensions (3.0.5 for Build and 3.0.3 for Release). Could you please try it and see if it resolves your problem?
Thanks
No more ""The database snapshot was saved by a newer version of SQL Compare" error
but now getting this.
no more getting this error
"The database snapshot was saved by a newer version of SQL Compare"
but start getting new one.
Please help.
Thanks
Gill
There might be a problem with our latest Powershell module then.
Could you please try to change your tasks to use version 3.1.10.3430? You can do that on your task definitions if you go to "SQL Change Automation version", pick "Specific" and enter 3.1.10.3430 on the specific version to be used and Save.
Does it help?
Version "3.1.10.3430", worked.
BUT, this is not good example, where you release latest version without proper simple testing.
Hope for quick fix.
Thanks
Gill
If that does not work please contact support so that we can have a closer look.
According to our build logs a few days ago we were getting ReadyRoll.MSBuild.3.0.19073.6043 and everything worked fine. Today we're getting ReadyRoll.MSBuild.3.0.19077.6044 which has this error.
Shouldn't a newer version be okay? We haven't done anything manually - this is just a new package that is automatically being provided by NuGet via the TFS add-on.
I don't see the 3.0.19073.6043 version on NuGet anymore - did it get removed? I'm guessing it had a newer version of SQL Compare than what is in the current version and since we had builds/deploys using that version we're getting this error now that the older version is being used.
On a dev system I deleted everything in __SchemaSnapshot and that got around it but I'd rather not do that for all our databases/environments.
- 3.0.19059.5510 had 13.7.3.9474
- 3.0.19073.6043 had 13.7.5.9770
- 3.0.19077.6044 has 13.7.3.9474
I'm guessing 3.0.19073.6043 had the new version of SQL Compare accidentally (or it had a bug) and it was yanked once someone realized and it was replaced with 3.0.19077.6044 that had the old version.
You can't do that! Now any databases done with the 3.0.19073.6043 version will have that error.
We've released version 3.0.19080.6206 which should solve your problem.
Hope it helps.