Database Reference
In-Depth Information
A second option that you can also use is the
Synchronize
command that allows
you to sync your development or test server with the production database.
Tip
For more information about this method, refer to the following section in Books
Online:
The third option that is commonly used to deploy projects to the production environ-
ments is using
Analysis Services Deployment Wizard
. This is a separate tool in-
stalled with SQL Server that will create the XMLA files that can be executed later on
the server using the files that SQL Server Data Tools creates during the build phase
of the deployment. These files are stored in the
<project folder>\bin
folder
and consist of the
.asdatabase
, the
.configsettings
, the
.deploymentop-
tions
, and the
.deploymenttargets
files.
The
.asdatabase
file contains the information required to create the database and
alltheobjects. The
.configsettings
filecontainsthedeploymentoptionsthatare
defined in the project. This also includes the data source string as well as the secur-
ity settings used when connecting to the data source. The
.deploymentoptions
file contains the deployment options such as if Transactional Deployment should be
used or if the database should be processed after deployment. Lastly, the
.deploy-
menttargets
files specify what server will be used during deployment.
As a user, you can either run Analysis Services Deployment Wizard interactively or
from the command prompt. When you run it interactively, you can use it to create
an answering file that later can be used for the deployment on the server. Using the
command prompt can be an effective way when scheduling the deployment, so that
it executes at a later stage.
Search WWH ::
Custom Search