Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server System Report


SQL Server System Report

Author
Message
Sean Smith (SSC)
Sean Smith (SSC)
SSC-Addicted
SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)

Group: General Forum Members
Points: 497 Visits: 959
Comments posted to this topic are about the item SQL Server System Report
HextallFanForLife
HextallFanForLife
SSC-Enthusiastic
SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)SSC-Enthusiastic (112 reputation)

Group: General Forum Members
Points: 112 Visits: 238
Great script!! Very uself....
Sean Smith (SSC)
Sean Smith (SSC)
SSC-Addicted
SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)

Group: General Forum Members
Points: 497 Visits: 959
Thank you! I hope it helps you out. Smile
amc-885860
amc-885860
Grasshopper
Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)Grasshopper (23 reputation)

Group: General Forum Members
Points: 23 Visits: 560
Hi, love this script! Thanks for taking the time to put this together!
This is coming to come in handly often. Thanks again Exclamation Mark
george25
george25
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 71
Sean

I've tried your script but get a whole load of errors (see below). I'd be grateful for your help as your report looks really useful.

Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 29
Line 29: Incorrect syntax near 'MAX'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 30
Line 30: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 37
Incorrect syntax near the keyword 'TABLE'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 39
Line 39: Incorrect syntax near 'MAX'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 40
Line 40: Incorrect syntax near 'MAX'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 41
Line 41: Incorrect syntax near 'MAX'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 45
Must declare the variable '@vRecipients'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 46
Must declare the variable '@vCopy_Recipients'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 62
Must declare the variable '@vXML_String'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 69
Must declare the variable '@vBody'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 145
Line 145: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 159
Incorrect syntax near the keyword 'FOR'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 185
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 185
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 213
Must declare the variable '@vFixed_Drives_Free_Space_Table'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 228
Line 228: Incorrect syntax near 'MAX'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 234
Must declare the variable '@vFixed_Drives_Free_Space_Table'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 243
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 257
Must declare the variable '@vBody'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 345
Must declare the variable '@vSQL_String'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 345
Must declare the variable '@vSQL_String'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 363
Line 363: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 375
Incorrect syntax near the keyword 'ORDER'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 383
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 402
Must declare the variable '@vBody'.
Msg 195, Level 15, State 10, Procedure usp_SSAJ_SQL_Server_System_Report, Line 443
'ROW_NUMBER' is not a recognized function name.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 468
Line 468: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 489
Incorrect syntax near the keyword 'ORDER'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 498
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 517
Must declare the variable '@vBody'.
Msg 195, Level 15, State 10, Procedure usp_SSAJ_SQL_Server_System_Report, Line 563
'ROW_NUMBER' is not a recognized function name.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 584
Line 584: Incorrect syntax near 'A'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 597
Line 597: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 612
Incorrect syntax near the keyword 'ORDER'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 621
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 640
Must declare the variable '@vBody'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 723
Line 723: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 734
Incorrect syntax near the keyword 'ORDER'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 742
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 760
Must declare the variable '@vBody'.
Msg 137, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 877
Must declare the variable '@vSQL_String'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 877
Must declare the variable '@vSQL_String'.
Msg 170, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 895
Line 895: Incorrect syntax near 'MAX'.
Msg 156, Level 15, State 1, Procedure usp_SSAJ_SQL_Server_System_Report, Line 907
Incorrect syntax near the keyword 'ORDER'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 918
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 937
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 971
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 979
Must declare the variable '@vBody'.
Msg 137, Level 15, State 2, Procedure usp_SSAJ_SQL_Server_System_Report, Line 988
Must declare the variable '@vRecipients'.
Sean Smith (SSC)
Sean Smith (SSC)
SSC-Addicted
SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)

Group: General Forum Members
Points: 497 Visits: 959
My pleasure! Smile
Sean Smith (SSC)
Sean Smith (SSC)
SSC-Addicted
SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)

Group: General Forum Members
Points: 497 Visits: 959
Can you give me some details such as what version of SQL Server you are using? Also, I know that if you are using some versions of IE that code on SQLServerCentral doesn't always copy / paste properly.
mlabedz
mlabedz
SSC-Enthusiastic
SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)

Group: General Forum Members
Points: 100 Visits: 91
Love the article. However it's going to talk a lot of work to make it Binary compatible. Unfortunately due to the nature of the beast we run all our DBMS in Latin1_Gen_Binary. As such, spelling and capitalization matter.

I always hate when really great articles end up in hours of frustration trying to retrofit the solution into Binary format.

Great article...
Sean Smith (SSC)
Sean Smith (SSC)
SSC-Addicted
SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)SSC-Addicted (497 reputation)

Group: General Forum Members
Points: 497 Visits: 959
Thanks for the feedback. Sorry it can't help you though. Sad
mlabedz
mlabedz
SSC-Enthusiastic
SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)SSC-Enthusiastic (100 reputation)

Group: General Forum Members
Points: 100 Visits: 91
Actually, I appologize. It was only 3 places with SYSNAME vs sysname.

Really Cool...
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search