Database Reference
In-Depth Information
Figure 19-2. A network share containing solution artifacts
Deploying the Files
When the files are gathered into one place, the next step is to deploy them to the test or production computers.
SQL Server, SSIS, SSAS, and SSRS all have different methods of deployment, making the deployment process very
complex. Let's take a look at some foundational things you should know.
This topic quickly gets into advanced administration and programming tasks that may be beyond your cur-
rent skill set. Just remember that until you become more advanced, you can always deploy your solution manually or
hire someone who specializes in release management.
Note
Manual and Automated Deployment
Deploying your files manually involves copying the files to a location that the computer's operating system can
use (such as a local hard drive or a network share) and running the SQL code and projects that you have included
in your Visual Studio solution. This means that a person is sitting at a computer, running the SQL code in SQL
Management Studio, starting the SSIS package, processing the cube, and uploading the reports.
Manual deployment works just fine if you only occasionally deploy the BI solution to new computers. In
many test environments, however, the solution may be deployed over and over again on the test servers. In those
scenarios, you may want to create some automation code to help streamline the deployment process.
Let's take a moment to give you some examples of how this kind of automation can be accomplished.
Deploying the Data Warehouse with SQL Code
The data warehouse must be in place before SSIS, SSAS, or SSRS can be deployed. Start by restoring a backup file
using code similar to that shown in Listing 19-1.
 
 
 
Search WWH ::




Custom Search