Database Reference
In-Depth Information
Figure 5-36.
Saving and publishing the SQL Scripts
Having a script file in addition to a database backup is practical for a couple of reasons. It is useful for
training new team members, familiar with SQL code, about the database design. Another advantage is that you
can include the script along with your business intelligence projects in a Visual Studio solution. Although this is
also true of a backup file, you cannot open a backup directly in a Visual Studio solution. With a script file, you can
simply double-click the file in Solution Explorer, and its contents conveniently display within Visual Studio.
■
The scripting tool generates working code but often adds more settings and features than you need in your
script. We use this tool to create the basic outline of the script and then modify it to remove any superfluous code
and add our own comments.
Tip
Organizing Your Files with Visual Studio
As you saw in Chapter 2, using Visual Studio to manage your BI solution files is practical because most of the BI
servers already store their files in Visual Studio projects. The exception to this rule is the SQL Server database
engine. This can be done in Visual Studio, but the means of accomplishing this can be quite obscure, especially
