SQL Server Team-based Development - Red Gate Software

207
Chapter 7: Maintaining a Code Library
Use of multiple files makes it much easier to develop versions and branches for each
individual code snippet and one can modify, add or delete files individually and safely.
Using a single file removes much of this flexibility, and modifying a single file makes it
likely that you will accidentally change code you didn't mean to change.
I strongly recommend maintaining a library of individual files. You can check them into
source control, and then share the directory with the team. You will also find it much
easier to work with, and maintain, these individual files in tools such as SSMS or Red
Gate SQL Prompt.
Tools for Creating and Managing Code Libraries
It is possible to simply use Notepad or WordPad within Windows, do a search against the
code and snippets to find what you need, and then copy and paste. However, that can be
a lot of work and there are, fortunately, better and more efficient tools with which to
manage your code library. For example:
• SSMS provides templates which allow us to define our own outlines for creating or
modifying database objects
• third-party text-editing tools, such as EditPlus, have built in snippet management
• wikis, for example TiddlyWiki or WikidPad, allow us to create a searchable database of
scripts, although these tools won't work well with source control
• advanced snippet and code management tools, like Red Gate's SQL Prompt, are also
available.
Over the coming sections, we'll discuss the benefits and limitations of each of the listed
solutions, but there are other options. You could even go so far as to use publicly available
online storage engines, such as SNIPPLR, from http://snipplr.com/.