This development model, by default, is used in the environment where every database developer has a copy of the same database on its SQL Server and connection between database developers are made through the SQL source control repository. All those information will be listed under the Connection section (between the and ):įor the ApexSQL Source Control 2021 version and higher, all database information are listed between “ DatabaseInfo” for that database (under the “ DatabaseName” will be listed that database name) and “ },” before the next “DatabaseInfo”: In the Options file all information about the repository path, chosen development model, database name, included/excluded objects, script options settings, etc.
The Options file, by default, is stored in the working copy of repository location, by default C:\Users\\AppData\Local\ApexSQL\ApexSQL Source Control: jsonīesides the framework objects created in the database, and the working copy of repository folders with all needed object scripts, the Options file will be created/updated as well during the linking process. Note: In ApexSQL Source Control 2021 version and higher, the extension of the Options file changed from.Note: It is strongly recommended that all scripts present in the database folder on the Working copy of repository location never be altered/deleted manually by the userĪll database folders in the Data folder on the Working copy of repository location will be created in the same way and contain the same type of information regardless of the chosen development model.Under the database folder, will be present all scripts that are necessary for the add-in to work properly on the linked database and to track changes against all linked objects from that database. Under the Data folder, will be created the SQL Server folder where will be created separate folders for every linked database from that SQL Server: Note: The Working copy of repository location can be changed after the database is linked, but once it is changed, it will be changed for all linked databases as well as the ones that will be linked in the future.
RecentConnection file – this file contains all information regarding the connection of the last database linked to the SQL source control repository.Options file – this file contains all options set in the Options window for every linked database from machine and user.
It contains information about the option set from the tabs where the Save as my defaults button is present and clicked
#Should apex sql autitor repository location how to
Use this article as a guide on how to manually unlink a database from SQL source control if for any reason automatic unlink does not give the expected results.Īt the same time the framework objects are created, during the linking process, the working copy of the repository will be created as well for the linked database. Besides that, a working copy of the repository (basically additional folders containing scripts for all database objects, from the database and the SQL source control repository) will be created on the machine where ApexSQL Source Control is installed for every linked database. This article will explain how to manually unlink a database from the SQL source control repository and remove all background files created by ApexSQL Source Control.ĭuring the database linking process to the SQL source control repository, based on the chosen development model, required framework objects will be created either in the database or on the SQL Server instance.
0 kommentar(er)
