For my previous two projects, the deployment of the BI project are varied.It is interesting that now am doing my third BI project on SQL Server and I got a easier way.
First One:
From my company's network server to the customer's server directly. Since it could not the deployed inside the SQL Server customized setting, what I have done is copying the xmla code to the server, and F5 run the xmla file. Then changing the data source and data source view parameters on the target server.
Second One:
The dev and test server are inside the client's network. So easily the servers could be set up inside the SQL server, using the NETWORK\SERVERNAME format.
Third One:
There is a utility ascmd.exe.
The
ascmd command-line utility enables a database administrator to execute an XMLA script, MDX query, or DMX statement against an instance of Microsoft SQL Server 2005 Analysis Services (SSAS). This command-line utility contains functionality for Analysis Services that resembles the
sqlcmd utility included with SQL Server 2005. For more information, see the topic
sqlcmd Utility in SQL Server 2005. The execution results of the script, query, or statement can be stored in a file together with relevant SQL Server Profiler trace information
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/12374161/viewspace-665034/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/12374161/viewspace-665034/