InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 20 Jun 2013 05:53:16 GMT20http://www.sqlservercentral.com/Forums/Topic869992-2624-1.aspxConfiguration:I have the following setup:1. One Dev VS2005 server (where I have installed VS2005) and created a SSAS project2. One Dev SQL2005 server where the data warehouse tables are located (Date dimension, Sales_statistics fact, etc) in the database engine and Analysis Service instance 3. One Production SQL2005 server database engine and Analysis Service instanceThere is a trust relationship from Dev to ProductionIn all tests I use Dev\administrator domain account.I also added Dev\administrator to Production SQL2005 Security and added SELECT rights to all the data warehouse tables (Date dimension, Sales_statistics fact, etc)I can do SELECTS, UPDATES DELETES to Production SQL2005 while connecting from Dev SQL2005 SSMS Situation:When I Process and deploy from Dev VS2005 server to Dev SQL2005 the Cube is properly deployed to the Analysis Services instance. I can open the cube database and access it from SSRS etc.When I Process and deploy from Dev VS2005 server to Production SQL2005 the Cube is NOT deployed to the Analysis Services instance. I get an error during the Process which states that Dev\administrator does not have access rights to Production tables. This happens only from inside Dev SSAS. In fact it is not really a Cube deployment problem but SSAS project cannot access the data warehouse tables on Production SQL2005 to start building the Cube.I have thought of installing SSAS on a Production server and build the cube and deploy it that way. I am almost certain that it will work but I do not want to put any dev tools in the Production environment. What Security settings do I need to get this set up to work.Sun, 21 Feb 2010 18:58:05 GMTnadeembc