Use source Safe for SQL Server to troubleshoot database version management issues

Brief introduction

Versioning is a well-known concept in the software development process. Because a project may require the participation of different role members, by using version control software, you can involve people of different roles in the project in parallel. Source control allows multiple versions of code to exist without confusing the code base, typically including bug fixes, adding new features, versioning, and more.

Although the development level of version control software is very mature, but at present there is no specific database-level version control software to help different actors in the database level of team collaboration, change code management and database changes to view and compare. The lack of version control tools at the database level may show the following scenarios:

Inability to collaborate at the database level: developer A's modification of the stored procedure causes the stored procedures created by developer B to be overwritten, thus unable to compare and track

Developer-development dba-testers are hard to collaborate on: SVN versions of tools are file-based and difficult to version control at the database level

Changes in the database are difficult to track: existing technologies cannot track who, at what time, what has been modified by the database, and when errors caused by the database or performance degradation are difficult to troubleshoot

Cannot record process assets for database changes: History of database changes only the database operators understand that these process assets are difficult to inherit when the relevant personnel leave or transfer

Difficult to audit the database: The existing database audit function often relies on the log, has a great impact on performance.

SQL scripts cannot be managed effectively: the existing practice is often to save SQL as a file and not to effectively manage and share

Cannot view the encrypted database object: If the object definition's original record cannot be found when an encrypted database object needs to be modified, the object must be overridden

SVN builds and uses complexity: The SVN usage process is too cumbersome for database personnel, adding additional workload to database personnel

As the database is the core of the whole business application, whether in the development environment or in the production environment, if not effectively solved, it will cause low productivity, the process assets can not be managed, the database review can not be carried out, difficult to troubleshoot the problems caused by the database changes.

Here's how source Safe for SQL Server solves this type of problem.

Installation of software

The software's official website downloads the installation package of source safe after the next step, after the installation is completed open management Studio, in the need to add to the source controller of a database server right button, in the pop-up menu select "Add Database to version control", as shown in Figure 1.

Figure 1. Adding a database to version control

Then set the relevant options, as shown in Figure 2.

Figure 2. Add database to version control related settings