This error can occur when using SQL Change Automation Powershell, with the default option of validating the schema folder in LocalDB, and you have LocalDB 2017 installed.
This is caused by a bug in LocalDB 2017 so you will need to install the latest Microsoft Update for LocalDB 2017:
https://www.microsoft.com/en-us/download/details.aspx?id=56128
An alternative workaround if updating LocalDB is not possible straight away, is to use the TemporaryDatabase or TemporaryDatabaseServer on the schema validation step (Invoke-DatabaseBuild), since setting either one of these will cause the tool to do the schema validation in a SQL Server instance rather than in LocalDB.
2
-2
Was this article helpful?
0 out of 2 found this helpful
Articles in this section
- Method not found: 'System.Security.CodeAccessPermission'
- Couldn't connect to the database specified by the Target parameter: A connection was successfully established with the server, but then an error occurred during the login process
- Could not install SqlChangeAutomation from any registered PSRepository
- System.Exception: No match was found for the specified search criteria and module name 'SQLChangeAutomation'. Try Get-PSRepository to see all available registered module repositories
- No match was found for the specified search criteria and module name 'SqlChangeAutomation'.
- Online index operations can only be performed in Enterprise edition of SQL Server
- Unable to resolve package source
- error 5(Access is denied.) while attempting to open or create the physical file
- SQL Change Automation Installation freezes at 99%
- SQL Change Automation Powershell permissions