The Full-Text Search Is Not Installed, Or A Full-Text Component Cannot Be Loaded error usually occurs because SQL Change Automation uses, by default, SQL LocalDB to validate the scripts folder.
SQL Local DB does not support Full-Text Search.
You'll need to use either the -TemporaryDatabaseServer or -TemporaryDatabase parameter on the Invoke-DatabaseBuild cmdlet (or, if using an add-on, use the corresponding parameter fields on the build step).
For example, if using Pipelines on Azure DevOps add-on you need to change the Temporary server type to SQL Server, you will then need to fill the server field with a valid instance name (the Database field is optional: if you fill it SQL Change Automation will use that Database to validate the schema, if not it will create a dynamically named database for that purpose).
Was this article 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