quote:

All good questions. But, one depends on the other. Here is how it all works.

Resource Analyzer records all kinds of information about each request as it’s being executed. Time of Day, elapsed time, cpu time, User, IO, Lines of output, etc. More than 100 items. This information is stored in SQL Server (relational) databases. Then over time, as data accumulates, you can run the reports we provide. Who is the biggest user in time, frequency, or data. What report runs the longest, which report does WHERE tests on fields that are not indexed, which columns from a table are never accessed, etc. All valuable information for tuning database tables or going to users to see why their report runs so long. As reports run over and over again, the system collects enough information to gauge how much resources each report is going to take.

Resource Governor lets an admin create run rules based on information collected by Analyzer. For example – Reports against the XYZ file that take over 5 minutes can’t be run on the last 2 days of the month or between 9am and 5pm. So it becomes a resource governor by stopping requests from running when you say they can’t. Most databases have a governor, but that only stops execution when so much time has expired. Resource Governor with the data collected can come up with a pretty darn close guess BEFORE the report even runs and then based on your rules – it executes or doesn’t.

So you would go with Resource Analyzer first and let it collect for a while before implementing Governor. You can enter the license code and activate them both together, then you configure them independently. You can tell Analyzer to collect information and don’t do anything with Governor.