SQL Server Team-based Development - Red Gate Software

BEGIN CATCH
IF @@TRANCOUNT > 0
BEGIN
ROLLBACK TRANSACTION
END
RETURN ERROR_NUMBER();
END CATCH
GO
Listing 7-7: A customized stored procedure template.
213
Chapter 7: Maintaining a Code Library
The key thing to remember, when customizing templates, is to strictly follow the
format for creating template parameters, namely . You're not required to supply either the data type or the default value, but the
parameter name must be identical everywhere it is referenced, or you'll simply create a
new parameter. Notice, in Listing 7-7, that Procedure_Name is referenced more than
once in the template definition.
If you save these changes, the default template will be overwritten to reflect the standards
you are attempting to implement within your enterprise. The modified template still
retains the functionality of the standard templates; CTRL+SHIFT+M still works and you
can fill in the parameter values as described earlier.
Just as you can edit existing templates, you can also create multiple new templates for use
within your system, storing them all within the Template Explorer, alongside the system
templates. Again, you just need to be sure that you keep a backup of the system templates,
and check all the templates into source control so that you can maintain versions and a
known change history.
While templates work well as a code generation and sharing mechanism for object
creation scripts, you'll also need to create and maintain smaller snippets of code,
such as the error handling routine shown earlier, and templates are not best suited
for this. To maintain a listing of partial code snippets for reuse in multiple scripts,
another mechanism is needed. One possibility is to use one of the advanced text
editors, such as EditPlus.