Source Control in SQLSourceSafe

SQLSourceSafe can maintain multiple versions of database scripts that are saved in text files, including a record of the changes from version to version.

SQLSourceSafe addresses the following areas:

Team coordination – make sure that only one person can modify a database item at any given time. This prevents database items from being accidentally replaced by another user's changes.
Version tracking - archive and track old versions of source code for database items, so that they can be rolled back to previous versions when needed.
Reusable or object-oriented code - track which programs use which modules so that code can be reused.

SQLSourceSafe provides version control and history services, to ensure that each version of a database item is recoverable. The date/time stamp is used to record when database items are created or checked in.

SQLSourceSafe uses three methods to track versions of files and projects:

Version numbers: These are internal numbers maintained by SQLSourceSafe. The user does not have control over these numbers. Every version of every database item has a version number. The version number is an integer starting at 1 and increased by 1 each time when a new version is checked in.
Labels: These are strings that you can associate to a version of database item(s). A label is a free-form string of up to 31 characters. The following are all valid labels: "1.0", "2.01b", "Field Test 3", and "Approved by QA".
Date/Time stamps: They tell when a database item was last modified (either created or checked in). SQLSourceSafe supports both 12-hour format (with "a" or "p" suffix) and 24-hour format.