What are the challenges you face when working across database platforms? Take the survey

Get LocalDB to SQL2017

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


Sign In or Register to comment.