Configure Analysis Services Project Properties (SSDT)
In SQL Server Data Tools (SSDT) , an Analysis Services project is defined with certain default properties that affect building and deploying the Analysis Services project.
To change project properties, right-click the Analysis Services project object and then click Properties. Alternatively, you can click Properties on the Project menu.
The following table describes each project property, lists its default value, and provides information about changing its value.
|Build / Deployment Server Edition||The SQL Server edition used to develop the project||Specifies the edition of the server to which projects will finally be deployed. When working with multiple developers on a project, developers need to understand the server edition to know which features to incorporate into the Analysis Services project.|
|Build / Deployment Server Edition||The version used to develop the projects||Specifies the version of the server to which projects will finally be deployed.|
|Build / Outputs||/bin||The relative path for the output of the project build process|
|Build / Remove Passwords||True||Specifies whether known passwords will be removed from connection strings that are written to the output directory during the build process. Passwords are removed to increase security. If passwords are removed, they will need to be provided when the deployed project is processed in order for Analysis Services to access the source data.|
|Debugging / Start Object||<Currently Active Object>||Determines that object that will be started when you start debugging.|
|Deployment / Deployment Mode||Deploy Changes Only||By default, only changes to project objects are deployed (provided that no other changes were made to the objects directly outside of the project). You can also choose to have all project objects deployed during each deployment. For best performance, use Deploy Changes Only.|
|Deployment / Processing Option||Default||By default, Analysis Services will determine the type of processing required when changes to objects are deployed. This generally results in the fastest deployment time. However, you can also choose to have either full processing or no processing performed with each deployment.|
|Deployment / Transactional Deployment||False||By default, the deployment of changed or all objects is not transactional with the processing of those deployed objects. Deployment can succeed and persist even though processing fails. You can change this default to incorporate deployment and processing in a single transaction.|
|Deployment / Target Server||localhost||By default, database objects within the Analysis Services project will be deployed to the default instance of Analysis Services on the local computer on which SQL Server Data Tools (SSDT) is being used. Change this default to specify a named instance on the local computer or any instance on any remote computer on which you have permission to create Analysis Services objects.|
|Deployment / Database||<project name>||By default, the name of the Analysis Services database in which the Analysis Services project objects will be instantiated upon deployment is the name of the Analysis Services project at the time it was defined. Change this property to change the name of database on the Analysis Services instance specified by the Server property.|
Properties are defined on a per configuration basis. Project configurations enable developers to work with an Analysis Services project with different build, debugging, and deployment settings without editing the underlying XML project files directly.
A project is initially created with a single configuration, called Development. You can create additional configurations and switch between configurations using the Configuration Manager.
Until additional configurations are created, all developers use this common configuration. However, during the various phases of project development — such as during the initial development and testing of a project — different developers will may use different data sources and deploy the project to different servers for different purposes. Configurations enable you to retain these different settings in different configuration files.