Category
主题
副主题
“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.
How to implement SQL Server source control using the shared development model (4211904)
Having a team of developers working on the same (shared) database can be challenging for many reasons. ... It is critical to ensure that all changes are properly tracked and that each developer is informed about the status of objects currently used by the rest of the team.
Automatically script SQL Server table data and object schema directly to source control (4299537)
Imagine a scenario where you want to get your database into source control quickly and easily, including all schema objects and data from certain code tables that won’t change aka Static data. ... Then, once you have ported your database successfully to source control, to be able to update the repository nightly with any and all changed objects.
How to version control SQL scripts alongside SQL database objects (4291853)
This article explains how SQL database source control can help in version control SQL scripts alongside SQL database objects. ... Developing a software sometimes requires versioning not only database objects, but custom SQL scripts for migration, configuration, automation or other purposes
How to make SQL database version control safer with branches (4290054)
As long as a separate branch is used to commit changes, a master branch can be used to deploy a working copy of a database from source control for any purposes. ... For the purpose of this article, a Git repository hosted on Bitbucket.org is used for SQL database version control, but the same applies to any other source control system that supports branching.
Revision history of an object change in a SQL database using Git (4300753)
The essence of each source control system is the ability to easily review the history of committed revisions. ... In addition, to comparing revisions, a user needs to get a specific revision and apply it against a database.
How to automatically synchronize SQL Server database schema changes to a source control repository (4301042)
In this article we will explain how to create a simple batch file to automatically synchronize database schema changes with a source control repository from any individual object changes detected in the database.
How to work with version controlled SQL Server database static data (4215959)
When working with SQL Server database static data in the context of version control, there are several key requirements. ... As a pre-requisite, static data should be properly linked and initially committed to the repository.
Integrate source control with SQL Server to reduce database development time (4210939)
Collaborating on database development introduces a series of challenges. ... For instance, having the development team change the tables, views, stored procedures and other objects in a single, shared database, although intuitive, can introduce severe issues down the road as valid changes can be lost or overwritten by an unsuspecting teammate.
How to use source control with SQL Server Management Studio (SSMS) (4289801)
The growing adoption of Continuous Integration development practice implies that developers have to work in a collaborative manner by storing and sharing their source code into a central repository.
How to commit SQL Server table static data to a source control repository (4290140)
Once a SQL database is committed to a source control repository with all of its objects, the next task is to commit the static data. ... Static data is non-transactional data from tables that generally don’t change often like postal codes, department names etc.
SQL Server Source control – Part I – understanding source control basics (4209656)
The goal of database source control is to propagate changes from a development environment, to test and production without issues and to fulfill the need to restore a database at any point in time, maintaining an audit trail, and to allow successful team collaboration during the project.
Three phased approaches to getting your SQL Server database into source control (4288730)
Database development teams show an increasing interest in getting their SQL Server databases into source control. ... However, depending on the team’s actual needs, their development plan and the level of source control integration required, there are various ways to achieve getting a database under source control.
SQL Server Source control – Part II – Integration (4211939)
Once become familiar with the source control basics (SQL Server Source Control – Part I – understanding source control basics), development client can be connected to both SQL Server and the version control system.
Synchronize SQL database changes between local and remote repositories in distributed source control systems (4214378)
Having a SQL database being version controlled locally, by storing all changes in a repository on a local machine can be quite handy. ... In the context of team based database development, it is necessary to establish the environment where changes can be tested locally, specific revisions reverted from the commit history, and doing such things before pushing changes to the remote repository where the rest of the team will be able to review them, and apply against a local database copy.
How to export a SQL database directly to source control (4289344)
ApexSQL Script allows to export complete SQL database, or just a couple of its objects, to one of the mentioned source control systems. ... Select a SQL database in the New project window and click the Open button:
Using SQL source control to track database changes (4213380)
The goal of this article is to explain how SQL database source control can help in auditing database changes. ... Tracking a change by itself is not the only task required for successful implementation of SQL source control, as we also want to know who made the change, when and why.
How to update a SQL database from source control while avoiding dependency errors (4300173)
Working with a database under source control has many benefits. ... Beside tracking all the changes made against a database, including the information what the changes were and who made them, you can also track history of committed versions of all database objects which can be restored on a database at any point.
How to see the full version history of a SQL Server database object under source control and, if needed, revert changes (4210873)
One of the main benefits of a SQL database version control is that any version of an object committed to the repository, is available through the revision history. ... With that being said, browsing the history allows seeing all versions of the specific database object, committed over time, and reverting any version from the history in order to apply it against a database.
How to implement SQL Server source control using the dedicated development model (4296072)
Having a SQL Server database under source control is rapidly becoming the norm vs the exception in many software development teams. ... Using any development model (dedicated or shared), requires the team to establish a workflow and a set of rules.
How to implement check out and lock policies in the shared database source control development model (4210872)
In a multi-user database-development environment, avoiding conflicts and overwrites with edits, and ensuring all changes are audited and recorded is important. ... Until recently however, effective tools for SQL development management have lagged well behind their client developer equivalents, like Visual Studio.
How to use the Change log feature in ApexSQL Source Control (4262433)
This article explains how to see changes in this SQL source control tool made by any developer against a database linked in the shared development model using the Change log feature. ... When working in a multi-developer environment where multiple changes occur in a database, it is helpful to have information about those changes at the minute they happen.
Minimal permissions for Azure SQL Database in database source control (4241106)
This article will explain the minimal needed users’ permissions for Azure SQL Database when ApexSQL Source Control is used as a database source control tool. ... The database source control environment supports working on Azure SQL Database which applies that more than one user will be connected to the same SQL Server.
How to commit changes from other users in the database source control (4253336)
This article explains how the user can commit changes that are made by other users on objects in the database source control. ... This database source control tool allows developers to chose in which development model the database will be linked in:
The Object status in the database source control (4289118)
This article explains how to see information about the object status in the database source control. ... ApexSQL Source Control supports two development models for the database source control: ... Dedicated – each developer has a local copy of a database on the local machine.
新产品关联性