Comments
1 comment
-
Hi @afu
If you're using a Windows hosted Agent in your pipeline, you will need to use the latest 2022 agent as this will be running LocalDB 2017, please seeĀ https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml
https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md
If you're using your own local agent, then you can follow these steps to upgrade your LocalDB
https://stackoverflow.com/questions/26897152/how-do-i-upgrade-sql-server-localdb-to-a-newer-version
Add comment
Please sign in to leave a comment.
We have updated and confirmed that all the databases on the target server and the LocalDB on the build server have the compatibility level 140. However, the build continues to fail with the error; we have removed the STRING_AGG function in order to keep moving forward but we would like to use more recent SQL functions.
Is there any other way to figure out what is still tying our CI/CD to SQL2014? Any help would be greatly appreciated. Thank you!