| title | Deploy Model Solutions Using XMLA | Microsoft Docs | ||||
|---|---|---|---|---|---|
| ms.custom | |||||
| ms.date | 06/13/2017 | ||||
| ms.prod | sql-server-2014 | ||||
| ms.reviewer | |||||
| ms.technology | analysis-services | ||||
| ms.topic | conceptual | ||||
| helpviewer_keywords |
|
||||
| ms.assetid | a8cb1837-fcac-4730-bea4-a72cf94d9f7c | ||||
| author | minewiskan | ||||
| ms.author | owend | ||||
| manager | craigg |
In [!INCLUDEssManStudioFull], the CREATE To option of the Script Database As command creates an XML script of an entire [!INCLUDEmsCoName] [!INCLUDEssNoVersion] [!INCLUDEssASnoversion] database or one of its constituent objects. The resulting script can then be run on another computer to recreate the schema (metadata) of the [!INCLUDEssASnoversion] database. The script generates the entire database, and there is no mechanism for incrementally updating already deployed objects when using the script. After running the script and deploying the database, the newly created database must be processed before users can browse it.
For more information about the Script Database As command, see Document and Script an Analysis Services Database.
When using the Script Database As command, you cannot modify specific properties (such as the database name, data source connection strings, and security settings) of the database objects. These properties must either be manually modified in the script after the script has been generated or modified in the deployed database after running the script.
Important
The XML script will not contain the password if this is specified in either the connection string for a data source or for impersonation purposes. Since the password is required for processing purposes in this scenario, you will either need to add this manually to the XML script before it executes or add it after the XML script executes.
Deploy Model Solutions Using the Deployment Wizard
Synchronize Analysis Services Databases