What we found out was that the users were using SSRS to make spreadsheets and reformat them and change them and add to them, etc, etc. We found that it was easier and produced results much more quickly to simply allow the users to call certain stored procedures from their spreadsheets. It still responds to AD logins correctly, etc, etc. And, the users hated SSRS because "it slowed us down a lot".
As for my morning reports for SQL Server, I wrote my own to create a little HTML and embed it in the email the server sends me every morning for SQL Agent Jobs across multiple servers and an Enterprise Disk Report that reports potential problems with disk space by server name and disk (including size, free space, etc) that covers about 148 servers (only a few of them are SQL Servers). That same report contains a "removable media" finder and it even includes "isDirty" and whether or not the server could be pinged and then logged into.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)