By default SQL Change Automation deploys changes within a transaction (and it uses the SERIALIZABLE transaction isolation level).
Full text objects can't be created inside transactions.
A SQL Change Automation build always start by deploying the project to an empty database (schema validation), so this issue is more likely to occur at this stage.
To workaround this issue you should use the NoTransactions SQL Compare option.
Please note that if you use this option there's no rollback if the deployment fails so it's advisable to isolate changes that require this change as much as possible and backup the targets before carrying out the change.
Setting the SQL Compare options in the Azure DevOps add-on:
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