Applies to

ApexSQL Source Control

Symptoms

After the linking process and initial commit is done objects with the special characters in their name will be listed only in the Repository column like they have not been committed at all. Those objects will be listed as the Custom script type under the Type column and the wrong schema will be listed under the Schema column.

Applies to

ApexSQL Source Control

Symptoms

The objects containing Windows reserved words in their name are committed to the source control repository with the 2021.01.2063 or 2021.01.2072 add-in versions. Upgrade to the newer add-in version is done, the Action center tab is opened but the already committed objects are listed.

Applies to

ApexSQL Source Control

Symptoms

“This database is already linked using the Dedicated model” info message is shown when trying to link a database to source control.

Applies to

ApexSQL Source Control

Symptoms:

Working with large databases can lead to the system out of the memory issue in SQL Server Management Studio.

Applies to
ApexSQL Source Control

Symptoms
After upgrading from the previous versions to 2015.03.0065 or higher, ApexSQL Source Control cannot detect the previously linked shared databases and a “The path is not of a legal form” error is encountered when opening the Action Center tab:

Applies to
ApexSQL Source Control

Symptoms
During the process of a database linking to Team Foundation Server located in a different domain from the host machine, ApexSQL Source Control will not be able to resolve a DNS address and an error will be thrown:

Applies to
ApexSQL Source Control

Symptoms
After upgrading ApexSQL Source Control from previous versions to version 2015 or higher, the previously integrated databases are no longer linked to source control.