Corruption of a SQL Server Analysis Services database
Atualizado em: 2009-04-30
Whether or not you have a Microsoft SQL Server 2005 Analysis Services database backup, an Analysis Services database can be regenerated at any time by performing full deployment for the model site on which the database was corrupted.
Perform a full deployment for the model site by using the Utilitário de Comando do Planning with the ModelSiteDeploy parameter and the /Full flag, as shown in the following example.
ppscmd modelsitedeploy /full /server <planningserver url> /path <applicationlabel>.<modelsitelabel>
A full deployment using Utilitário de Comando do Planning will first drop the existing corrupted Analysis Services database, and then re-create the database.
.gif "Observação") Observação: |
|---|
Any customized configuration settings on the Analysis Services database will be lost after the full redeployment of the model site. Manually reapply those settings to the Analysis Services database after the full deployment is complete. |
If you have an Analysis Services database backup, you can choose to restore the database backup only if you know the Analysis Services database is in sync with application database data.
| Observação: |
|---|
If the Analysis Services database backup is not in sync with the application database data, do not use the backup. Instead, perform the full redeployment of the model site to create a new Analysis Services database that matches the application database data in the event of corruption of the Analysis Services database. |
.gif "Importante") Importante: |
|---|
The Deployment menu option within Planning Business Modeler is to be used only for incremental deployments of the Analysis Services database. In the event of a database corruption, incremental deployment of the Analysis Services database should not be used. Using the PPSCmd ModelSiteDeploy /Full option is the only way to perform a full deployment of the Analysis Services database. |