How can we help you today? How can we help you today?
Sergio Rocha
That folder isn't in a Git repository error
You will get this message when you choose Git when attempting to link your database to a Version Control System and link it to a folder that isn't a git repository. To avoid this error message you ...
Edited 1 follower 0 comments -1 votes
Why we don't recommend using Shared Mode with Git
We don't recommend using Shared mode with Git; here's an example of why: Our database development team is Alix and Bob.  Alix and Bob develop against a single, shared database. They use SQL Source ...
Edited 1 follower 0 comments 3 votes
The 'SqlSourceControlPackage' package did not load correctly
This issue can have multiple causes: Using an outdated SQL Source Control version SOC is compatible with the versions of SSMS available at the time of its release. It is good practice to always ...
Edited 2 followers 0 comments -22 votes
Cannot use a CONTAINS or FREETEXT predicate on table or indexed view 'object_name' because it is not full-text indexed
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 Chang...
Edited 1 follower 0 comments -2 votes
The partition scheme [xxx] on table [yyy] was not found
1. Make sure the repository folder which the database is linked to is solely used by SQL Source Control for that database (it's important to not manually add anything to the folder unless for troub...
Edited 1 follower 0 comments -32 votes
Full-Text Search is not installed, or a full-text component cannot be loaded
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...
Edited 1 follower 0 comments -5 votes
The operation could not be performed because OLE DB provider ... for linked server ... was unable to begin a distributed transaction (SCA)
This error occurs because of the Transaction Isolation Level. By default, SQL Change Automation for Powershell uses the Serializable Transaction Isolation Level, however this deployment requires a ...
Edited 1 follower 0 comments 0 votes
Post-update schema check failed
This error can occur when Deploying a Database Release (which corresponds to the Use-DatabaseReleaseArtifact if using Powershell) On this step, SQL Change Automation will deploy an update script ge...
Edited 1 follower 0 comments -1 votes
Pre-update schema check failed
This error can occur when Deploying a Database Release (which corresponds to the Use-DatabaseReleaseArtifact if using Powershell). On this step SQL Change Automation attempts to deploy an update sc...
Edited 1 follower 0 comments -3 votes
SQL Change Automation Licensing
SQL Change Automation (SCA) is licensed per user. All SQL Developers contributing to a Database project that's automated by SCA should have a Flyway Enterprise license. SCA is not sold as a standal...
Edited 1 follower 0 comments -11 votes