| Although using source control systems is fairly straightforward, there are a few practices that you should be aware of to help you avoid some of the inevitable source control gotchas. The following are a few suggestions for better source control practices: Ensure that the default directory is uniquely defined for each developer on the team. If you specify a shared location for the default directory, you'll have overwrites regularly. Ensure that you check in changes to the solution or project as soon as possible because the project and solution files are impacted by all filename changes. The default setting for allowing multiple checkouts of the same file is off. Keep it that way, especially if you edit multiple packages simultaneously. As previously mentioned, packages don't merge well. Keep files checked out only so long as you must. If you have exclusive checkout turned on, especially on large teams, you might be prohibiting others from editing a file. If you need to see who has a file checked out, select the file in the Solution Explorer, choose File, Source Control, and then SourceSafe Properties. When opening solutions, use the Get Latest Version option. This updates your current solution files so that you can receive the latest changes from others on your team. Before checking in files, always get the latest version of the other files in the solution before testing your changes and checking in. This ensures that your changes will work correctly against the changes others have made in the same project. Avoid asymmetrical checkins. Asymetrical checkins are when you check in one file in a change but not another. For example, if you change the name of a file in a project and update the project, you should check in both the project file and the file. Otherwise, when others sync on the project, it will be broken. Always do diffs, even on packages. Although it can be difficult to understand what's happening in a package, you can do a sanity diff check. For example, if you do the diff and you see that there is a new executable named "You are a dork," you'll know that there's something amiss in the package. You don't even have to know what that task is. You'll just know that you didn't put it there.
Source Control in SQL Management Studio SQL Server Management Studio also supports the Project Explorer and source control. Although the types of files that the Management Studio solutions manager contains are constrained to connections, queries, and other miscellaneous files, the same source control features like the Solution Explorer icons, Source Control toolbar, and Pending Checkins window are all there. You enable source control in the same way as in BIDS. If you have scripts that are related or part of a project you're building in BIDS, consider storing both in the same node in the source repository. This makes it easier to move, back up, restore, and manage the entire solution over time. |
|
