2. Building A Performance Data Warehouse for SQL Server CPU & Disk Activity By Brian Flynn Information Technology Renaissance Man http://www.linkedin.com/in/brianpaulflynn Based on presentation given to St. Louis SQL Server Users Group on 9/11/2007 http://www.stlssug.org/docs/Using_Analysis_Services_To_Analyze_SQL_Server_Activity.ppt http://www.stlssug.org/docs/Using_Analysis_Services_To_Analyze_SQL_Server_Activity.ppt

3. Tools Required SQL Server RDBMS Analysis Services Excel Microsoft Paint

4. Capture CPU & PIO Every Minute

5. Calculate Deltas in a View Create a “Delta View”  One of the secrets to creating a good cube based on CPU & PIO data recorded every minute is calculating the deltas.  To match up from one minute to the next, use LoginTime, ProcessID & ContextID together.  Look out for NULLs

6. Analysis Services 2000 Cube I’ve used this AS2K cube design since 2001. It’s been so reliable I haven’t needed to upgrade it.

7. Analysis Services 2005 Cube As a proof of concept I created this design for SQL 2005. It will probably run on SQL 2008 as is. The only difference is how the time dimension is managed.

8. Scheduled Job(s) Single Server vs. Multi-Server Setup  Depending on if you do everything on one server or only gather data on the production server & use a separate server to process the data will determine your specific job definition(s). Gather data for 15 minutes, stop gathering, incrementally update cube & restart the gathering.

9. Visually Identify The Smoking Guns

10. Leverage Application Names in Connection Strings

11. Leverage Host & Usernames* *Very Useful With Integrated Authentication

12. Leverage Default Catalog (DB) Comparing 4 Weeks At Hour Level

13. PIO By Day Over 2 Months

14. PIO By Day Over 6 Months

15. Quantify The Effectiveness of Changes

18. How Precise & Reliable Is It? This system has run for 10 years Minute by minute resolution enables detection of brief spikes that escape traditional reports. If a connection opens, executes and closes in between polling cycles, it will go undetected.

19. Cost Benefit Ratio Requires minimal resources Eliminates the need to spring into action Discovers needles in haystacks! Has been useful to prove/disprove tactical configuration changes. Plan for capacity of disk subsystems.

20. Thank You & Good Luck! Contact me via LinkedIn if you have any questions. http://www.linkedin.com/in/brianpaulflynn