BI for the DBA


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

BI for the DBA

  1. 1. Michelle Gutzait Michelle.gutzait@gmail.comBlog:
  2. 2.  Introduction Multi server management via:  Linked Servers  SSMS  SSIS  SSRS  PowerPivot  Powershell
  3. 3. Whoami? SQL Server Consultant@  24/7 Remote DBA services
  4. 4.  Backup age and Recovery Models Versions and editions of SQL Server and OS Database sizes and free space Configured Linked Servers SQL Server logins SP code versions Etc….
  5. 5.  Manual (server by server) Linked Servers SQL Server 2008 SSMS Multiserver Management Integration Services Excel and PowerPivot Reporting Services SQLCMD/osql PowerShell
  6. 6. Linked Servers Populate a table with list of SQL instance names Loop over the server names in the table  If Linked Server does not exist:  Create Linked Server  Add a flag  Fetch data from remote server into a local table  If Linked Server needs to be dropped (flag):  Drop Linked Server  Select all collected information
  7. 7. SQL Server 2008 SSMS(Multi server queries)
  8. 8.  Populate a table with list of server names Loop over the server names in the table  Connect to the server  Import information into a local table
  9. 9.  Download Power Pivot (Office 2010) Open Excel Sheet Run queries via Power Pivot or Excel Sheet Connect to servers Pivot Tables and Pivot Charts Link information via Power Pivot
  10. 10.  Populate a table with list of server names Get server name as a parameter  Connect to the server  Query the data as a reportConnection string will be: = "data source=" & Parameters!ServerNames.Value & “;initial catalog=master"
  11. 11.  Create an SQL file as input file Execute CMDSQL or osql for each server, with the above input file You may want to “format” the results
  12. 12.  Prepare a text file with all instance names Prepare an input file with the SQL command(s) Execute the SQL command(s) for every instance in the file
  13. 13.  Performance Dashboard Template Explorer
  14. 14.  Monitored SQL Server instance must be SQL 2005 SP2 or later Run the Setup.sql file on each monitored (SQL 2005+)  A bug (cpu_ticks_in_ms  cpu_ticks) Open the performance_dashboard_main.rdl file with the Custom Reports in SSMS
  15. 15.  Set of templates  Out-of-the box  Customized
  16. 16. Questions? Feel free to contact me: