Post reply

SQL Server System Report

  • May 15, 2010 at 4:18 am

    #219006

    Comments posted to this topic are about the item SQL Server System Report

  • May 24, 2010 at 11:01 am

    #1171678

    Great script!! Very uself....

  • May 24, 2010 at 11:03 am

    #1171679

    Thank you! I hope it helps you out. 🙂

  • June 14, 2010 at 5:05 pm

    #1180149

    Hi, love this script! Thanks for taking the time to put this together!

    This is coming to come in handly often. Thanks again :exclamationmark:

  • June 17, 2010 at 5:25 am

    #1181473

    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'.

  • June 17, 2010 at 6:16 am

    #1181493

    My pleasure! 🙂

  • June 17, 2010 at 6:17 am

    #1181496

    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.

  • June 17, 2010 at 6:17 am

    #1181497

    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...

  • June 17, 2010 at 6:20 am

    #1181499

    Thanks for the feedback. Sorry it can't help you though. 🙁

  • June 17, 2010 at 6:23 am

    #1181500

    Actually, I appologize. It was only 3 places with SYSNAME vs sysname.

    Really Cool...

  • June 17, 2010 at 6:27 am

    #1181504

    Fantastic! Great to hear. 🙂

  • June 17, 2010 at 7:23 am

    #1181545

    Great article. Fits in with a project that I am working on.

    Just to try it out, I ran as script on my development machine (SQL Server 2005) without creating the proc and output the body content to text or a file.

    The output is greatly truncated at the Database Recovery Model section. Maybe some nulls getting concatenated somewhere?

  • June 17, 2010 at 7:30 am

    #1181550

    Hmmm... would need to see the output. Send it to me if you want (email address is in the script).

  • June 17, 2010 at 11:49 am

    #1181762

    This the report I've been looking for all my life. Thank you! 🙂

    Just one little thing, it runs terrific on SQL2005 but not at all on SQL2000. Is it possible that you might have SQL2000 version???

    Thanks again, I can really use this report.

  • June 17, 2010 at 11:53 am

    #1181765

    Sorry, there is no 2000 version (and unlikely that I'll be making one).

Viewing 15 posts - 1 through 15 (of 189 total)

You must be logged in to reply to this topic. Login to reply

Cookies on SQLServerCentral

This website stores cookies on your computer.

These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.

To find out more about the cookies we use, see our Privacy Policy