I am trying to determine how to idle a project during the warehouse build so that users are not able to run reports until the build is completed. Here is our setup:
Server A: MicroStrategy Intelligence Server (incl Metadata)
Server B: MicroStrategy Web Server
Server C: Warehouse SQL Server (contains no MicroStrategy components)
Sometime during the night, Server C gathers data from our mainframe via stored procedures and DTS packages. Given the volume of data, this process usually takes several hours to run. In addition, the exact time that it runs can vary from day to day based on when the mainframe has completed all of the prerequisite jobs.
We have users that access data around the clock; however, I need to idle the project when Server C is gathering the data so that users do not receive incomplete or incorrect data on their reports. I want to minimize the time that the project is down by idling the project when Server C starts its work and resuming the project when Server C completes its work.
The only way that I know of idling and resuming a project is to set up idling and resuming events based on triggers. However, the only way that I can trigger these events automatically is to tell our warehouse build to execute Command Manager scripts. This means that we would need to install MicroStrategy on Server C, our warehouse server, just to get the Command Manager scripts to run. (I tried running these scripts on a machine that doesn't have MicroStrategy components installed, and I simply receive error messages referring to missing components, dll's and the like).
Is there any other way that I can idle a project? Is there some record in the metadata whereby I could just tell the warehouse build to update a column value via SQL to idle a project and then update the same column value at the end of the warehouse build to resume it?
Thanks for your help.
Server A: MicroStrategy Intelligence Server (incl Metadata)
Server B: MicroStrategy Web Server
Server C: Warehouse SQL Server (contains no MicroStrategy components)
Sometime during the night, Server C gathers data from our mainframe via stored procedures and DTS packages. Given the volume of data, this process usually takes several hours to run. In addition, the exact time that it runs can vary from day to day based on when the mainframe has completed all of the prerequisite jobs.
We have users that access data around the clock; however, I need to idle the project when Server C is gathering the data so that users do not receive incomplete or incorrect data on their reports. I want to minimize the time that the project is down by idling the project when Server C starts its work and resuming the project when Server C completes its work.
The only way that I know of idling and resuming a project is to set up idling and resuming events based on triggers. However, the only way that I can trigger these events automatically is to tell our warehouse build to execute Command Manager scripts. This means that we would need to install MicroStrategy on Server C, our warehouse server, just to get the Command Manager scripts to run. (I tried running these scripts on a machine that doesn't have MicroStrategy components installed, and I simply receive error messages referring to missing components, dll's and the like).
Is there any other way that I can idle a project? Is there some record in the metadata whereby I could just tell the warehouse build to update a column value via SQL to idle a project and then update the same column value at the end of the warehouse build to resume it?
Thanks for your help.