Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 22 Feb 2002 @ 09:31:25 GMT


     
  <Prev Next>   <<First <Prev
Next>
Last>>
 


Subj:   Re: MicroStrategy 7.1
 
From:   Andrew Doorey

We are using Microstrategy 7.1.2 on V2R4. We do not use DBQM to restrict access to the users, but there are controls within Microstrategy to limit the load users can put on the machine. At project level you can limit the number of jobs a user can run. The drawback with this though is that if you set the limit to 5 then the user can only start 5 jobs - if they try to run any more they get an error rather than have them queued up. You can also limit the total number of database connections that Microstrategy can have. It causes the jobs to be queued until a database connection is free to be used. This limits the load on the data warehouse although it doesn't stop an individual user starting a large number of reports and hogging the system.

We make use of the report caching facility within Microstrategy to limit the amount of work done during the day. Depending on how much ad-hoc work your users need to do then this may be useful for you too. If you create standard reports which cover the basic queries users are likely to run you can then schedule them to run out of office hours. This stops different users building similar reports which would be run seperately.



     
  <Prev Next>   <<First <Prev
Next>
Last>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016