Catégorie
Rubrique
Sous-rubrique
How to work with ApexSQL Source Control in offline mode (4296783)
Developers check out files from a central server, make changes, and commit them back to a server. ... Working copy of the scripts is kept in the local system, while the revision history is stored only in the central repository.
How to associate a changeset with a Team Foundation Server work item ID (4214818)
Summary ... This article describes how a Team Foundation Server work item can be associated with a changeset prior to performing a commit operation. ... Description ... After linking a database to a Team Foundation Server repository each changeset that is ready to be committed can be associated with a work item in the commit message.
How to link a SQL Server database to a Perforce repository (4218142)
<p> ... Linking a database to a cloud repository is already covered where the Perforce repository hosted on Assembla.com is used as an example. ... Detailed information about using the cloud based Perforce repository on Assembla.com can be found in the <a href="https://knowledgebase.apexsql.com/how-to-link-sql-server-database-to-an-assembla-com-repository-using-perforce/" target="_blank">How to link a SQL Server database to an Assembla.com repository using Perforce</a> article.
ApexSQL Source Control framework objects inventory (4214511)
This article gives an overview of additional database objects (called framework objects) that ApexSQL Source Control creates on initial database linking to a source control repository ... When linking a database using the dedicated development model, the following objects will be created:
Checking out and checking in objects (4302275)
Check out and Check in features are available only when using the Shared database development model in ApexSQL Source Control. ... To Check out an object, right click an object in the Object Explorer pane, and select the Check out option from the context menu:
Differences between the dedicated and shared development models (4289016)
Summary ... This article provides a general explanation about dedicated and shared development models including implementation differences with ApexSQL Source Control. ... Description ... The Dedicated model means that each developer has a separate, local copy of a database(s) on a local machine.
Historical view (4211226)
This article explains how to see database and single object history, and how to apply one of the previous versions of an object in ApexSQL Source Control. ... Description ... Every source control system keeps track of the history of committed objects or object changes.
Change log FAQs (4214757)
This article provides answers to FAQs about the Change log feature in ApexSQL Source Control. ... A: The Change log feature provides the user with the information about any DDL change in a database including which user changed an object, when the change was made, and on which object.
How to link a SQL Server database to a Team Foundation Server repository (4213613)
article as the same steps are needed for any version control system. ... We’ll focus on specific settings and required information when TFS is the selected version control system. ... </p> <p> ... In addition to this, a TFS user can be any other Windows account or group that is in the same domain as the machine where TFS is installed.
How to utilize branching and merging with Git (4213581)
Summary ... This article describes how to utilize the branching feature when a SQL Server database is linked to a Git repository. ... Branching means to diverge from the main development line for any of the following reasons (working on a new feature, fixing a bug, etc.).
How to add NOT NULL constraint to a column using a migration script (4216108)
Summary ... This article describes specific use case when a NOT NULL constraint needs to be added to a column that does not have a DEFAULT constraint specified. ... Without a DEFAULT constraint, applying such a change on another database will fail.
How to link a SQL Server database to a Git repository (4211282)
This article describes how to link a database to a Git repository on various offerings of Git including Git on a local file system, online Git repositories as well as Git hosted on Team Foundation Server.
How to utilize branching and merging with Perforce (4211447)
Summary ... This article describes how to utilize branching and merging when Perforce is used as a source control system. ... Similar to Team Foundation Server, and Subversion, branching in Perforce assumes that a new folder is created for each new branch and that the content from a folder representing a source branch is copied to a folder representing a target branch.
Advantages of using Native drivers vs. CLI version control (4210579)
This article describes advantages of using Native drivers comparing to the <strong>CLI</strong> option. ... As an example, Git is the source control system we’ll use through the article. ... This file is automatically created in the add-in intermediary location when the user chooses the <strong>CLI</strong> option in the source control wizard.
How to upgrade legacy infrastructure in the Shared model (4297209)
</p> <p> ... The information about each new user who linked the same database was added in already created framework table upon linking a database. ... In this way, the team choose where to keep framework database objects <strong>for each database</strong> that is linked using the <strong>shared</strong> model.
How to save time linking to multiple databases by sharing mappings to other team members (4214914)
Having a solution that involves one user linking databases from a single machine, allowing the rest of the team to “import” these settings would save a lot of time. ... </p> <p> ... The team must use a shared SQL Server instance which hosts all the databases that need to be linked.
Object status icons and visualization (4296357)
When working in the Dedicated model, there are two different icons that can be shown in the Object Explorer pane. ... As soon as a database is linked to the repository, all objects that are selected to be version controlled in the Object filtering step will have the default “version controlled” icon in the Object Explorer pane:
Working folder (4214891)
This article describes how to use the Working folder feature. ... In addition, features that are not available when using the Working folder feature, and that are available when using any other supported source control system, are mentioned.
Permissions in ApexSQL Source Control (4216308)
Summary This article explains what are minimal permissions needed for the user to version control a database using ApexSQL Source Control. ... In addition, the article covers how to grant needed permissions to user.
How to install ApexSQL add-ins and integrate them into SQL Server Management Studio and Visual Studio (4296678)
In this article we will explain how to install ApexSQL add-ins and integrate them into SQL Server Management Studio and Visual Studio. ... Installation of ApexSQL add-ins can be done in two ways:
Setting up the Source control wizard for a Git repository (4216313)
This article explains how to set up the Source control wizard for the Git repository in ApexSQL applications. ... Description ... A prerequisite for setting up the Source control wizard in ApexSQL application is creating a repository on one of the hosting services.
Minimal SQL Server permissions for ApexSQL Developer tools (4216304)
Description ... In order to properly use ApexSQL Developer tools certain minimal SQL Server permissions need to be allowed on databases that are being used. ... Required permissions ... Required permissions are public SQL Server role and the public role membership that need to be configured along with the login.
How to maintain SQL database changes working with Git branches (4210578)
In case of database development, in the same way as for the application development, there are always tasks such as developing a new feature, fixing bugs from the current release, experimenting with code in order to improve performance, usability in any way and so on.
How to link and initially commit SQL Server database static data (4209482)
Non-transactional data in tables that is never (or rarely) changed, for example currency codes, postal codes or personal ID numbers, is often referred to as “static data” (also known as lookup or reference data).
“What broke my database?” Using SQL database source control for forensic auditing and database troubleshooting (4289268)
Besides the auditing trail of all the changes made against a database and having the information of who committed what and when, the main benefit of having a database under version control is the fact that the history of all the previously committed versions of any object (or a group of objects) can be used to find the exact version that broke the database at any point.
Nouvelle association de produits
- Outils libre-service
- Base de connaissances
- Notifications et alertes
- Support produits
- Téléchargements de logiciels
- Documentation technique
- Forums utilisateurs
- Didacticiels vidéo
- Flux RSS
- Nous contacter
- Support Technique
- Afficher tout