Professional SQL Server™ 2005 Administration

Chapter 10. Change Management

The challenges of the database administrator have changed drastically since the days of SQL Server 2000. Laws such as HIPAA and Sarbanes-Oxley have caused a DBA's job to become much more ritualistic because of trying to follow policies. In this chapter, you will learn how to create projects for your SQL Scripts and how to integrate those into Source Safe. You'll also learn how to monitor for unauthorized changes by using DDL triggers.

Creating Projects

Visual Studio Projects are generally a foreign concept to DBAs, as the concept originated from the programmer world. The hierarchy in Visua Studio is that you create a solution, which could contain many projects, which could contain many files for the project. For example, you may have a solution called LoanApplication that contains two projects: one for your C# program and another for the DDL to create the database. In the business-intelligence world, these solutions help you group all the related files together, like SSRS reports, SSAS cubes, and the SSIS packages to load the data.

Inside Management Studio, you can create projects as well to hold your scripts and connections for easy access. When you double-click a script, it will automatically connect to the connection associated with the script. By storing it in a project, it enables you to store files easily into Source Safe. This enables you to be able to check code in and out, allowing for a collaborative development environment where only one DBA ...