Comments
6 comments
-
-
I have the same (or at least, a similar) issue - I'm using the "RedGate SQL Change Automation Build" task within an Azure DevOps pipeline, using LocalDB, not a hosted instance. I previously had issues using Full Text Catalogs, which I was able to work around by setting the SQL Compare options to ignore Full Text. I can't ignore this particular change though, as it's a core part of the schema.
Is there any way to get the SQL Change Automation task to use an SQL 2017 compatible version of LocalDB? *Without* having to resort to using an actual SQL Instance. -
I'm having the exact same issue with Azure DevOps pipeline with "RedGate SQL Change Automation Build" task failing when we use STRING_AGG function. Has this issue really been going on for 3 years?
-
Is there any update to this?
-
Hi,
In this case, you will need to upgrade your version of LocalDB, you can check the current version using this link: https://knowledge.autodesk.com/support/advance-steel/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-check-the-version-of-your-database-in-Advance-Steel.html
To upgrade, you can follow the steps here: https://stackoverflow.com/questions/26897152/how-do-i-upgrade-sql-server-localdb-to-a-newer-version -
I got past this issue by going straight to upgrading to localdb 2019.
localdb 2017 had a bug in it where it was not appending the slashes correctly in the mdf file paths.
Add comment
Please sign in to leave a comment.
What is the best way to remedy this?
We currently target an Azure database. If we set the shadow db to our target connection string (Azure) we receive an error that states "The shadow database cannot be deployed to an instance of Microsoft Azure SQL."