Rick Romack (3/16/2009)

---

Great article and I can already see many uses. One thing I did find is that the tSQL scripts to install the jobs assumes that the SA account has not been renamed. On All our servers we rename that account even though we use Windows Only Authentication. I simply edited the script and changed the SA account to the account we use.

mishaluba (3/21/2009)

---

Thank you for the article and detailed solution. I had no idea that RS reports could be made so interactive using "Actions". Learning something every day!

scotta_miller (3/23/2009)

---

Thanks, for a Great article. I am trying to implement this on a test server and the report shows no data at all (Except the server name). When I run the stored procs by them selves I get data back. Any idea why the report is blank?

scotta_miller (3/23/2009)

---

Reporting Services 2005 and all servers are SQL 2005.

I followed the doc included in the zip file. In reporting services The servernames Dataset returns the correct server name, I checked and the default servername is setup in the report parameters. I had to mod the Credentials setting to use windows authentication for the dymanic connection. I have tried setting all the datasets to use the AppDB.rds and statically assign the single server and still the report is blank. If I copy the Stored procs from the data tab and run them in SQL they return data .



EXEC [dbo].[rpt_Tempdb_Occurrences_LowestNumberUnallocatedExtentPages] @Top = 20 --- Returns 16 records

EXEC [dbo].[rpt_Tempdb_Occurrences_HighestNumberVersionStorePages] @Top = 20 --- Returns 20 records


EXEC [dbo].[rpt_Tempdb_Occurrences_HighestNumberMixedExtentPages] @Top = 20 --- Returns 20 records

I have created the Utility DB and I put the TempdbSpaceUsage_ServerNames table inside that DB, I have ran all the scripts to create the table and stored procs along with the JOB Script. I am not sure what I did wrong.

Please let me know what additional information you need???