We have recently made our first foray into AWS for running SQL server. My first impression was, "What happened to my sa account!?!?".
After getting over the shock of not having full rights to perform monitoring and maintenance of the server I started installing our standard tools to see which would work. By putting the stored procs in our DBAWORK database I was able to get everything running except for seeing the detail on running processes.
I then remembered and excellent tool that I have used before, Microsoft SQL Server 2012 Performance Dashboard Reports.
Now I am excited, I can dig into the performance of the server and be able to share my findings with the rest of the team with pretty graphs and tables. I run the install with repointing the stored procs to DBAWORK, open the base report, and NOTHING.
The problem is that the install scripts and reports all use msdb as their install database. A quick review of the code and report definitions shows that it should be simple to change the database and get everything working.
To save you the suspense, it worked. If you want to add a DBAWORK database you can use my modified scripts and reports as is. If you want to customize for your needs replace DBAWORK in all the attached files with your preferred database.
