Get LocalDB to SQL2017

pfiorella

We recently added a script that makes use of the STRING_AGG function in SQL. This is a new SQL 2017 function. When we refresh our SQL Change Automation project, it fails script verification due to the shadow db using LocalDB which is running SQL 2016.

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."

Russell D

Did you get the error after following https://documentation.red-gate.com/sca3/tutorials/worked-examples/working-with-a-database-hosted-on-azure and https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/validating-change-scripts/development-and-shadow-databases?

AndrewStevens

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.

dbriskin

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?

StefanZ

Is there any update to this?  

DanC

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

StefanZ

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.