SQL Clone
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)
Right there with Babe
Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)

Group: General Forum Members
Points: 741 Visits: 990
It's pointing to the correct db mail profile and you changed the email address in the proc, correct?
anapatterson
anapatterson
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 350
Yes. I believe I figured out what the problem was. It just so happens that the 2008 servers are larger servers and therefore have more databases, indexes, etc. After confirming in the system views that the mail indeed showed "sent" I suspected it had something to do with the data itself so I changed the "body" to print "test" and it went through fine. I suspected that it may have been the size of the data in the @vBody variable so I commented out the "unused indexes" section and ran it again and it went through fine. I then tried changing it to send the output in an attachment with the parameter to allow for the longer length fields and it indeed erred out with a size limit. So, I believe the mystery is solved.
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)

Group: General Forum Members
Points: 741 Visits: 990
Good news. Thanks for sharing the solution. Smile
UDBNT
UDBNT
Old Hand
Old Hand (397 reputation)Old Hand (397 reputation)Old Hand (397 reputation)Old Hand (397 reputation)Old Hand (397 reputation)Old Hand (397 reputation)Old Hand (397 reputation)Old Hand (397 reputation)

Group: General Forum Members
Points: 397 Visits: 208
Sean, love the report (but for me it doesn't produce anything for the scheduled SQL jobs recently run?).

You seem to have a list of improvements/additions from the various respondees, so any idea when the revamped version is going to arrive?

More power to the efforts put in by the likes of yourself, as sharing the 'tricks' of the trade all helps make our lives a lot easier.

Thanks.
SQL_Padre
SQL_Padre
SSC Journeyman
SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)SSC Journeyman (93 reputation)

Group: General Forum Members
Points: 93 Visits: 583
Would it be possible to run this script from a "central server" and using Linked Servers collect data from remote servers?

SQL Padre
aka Robert M Bishop

"Do or do not, there is no try" -- Yoda
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)

Group: General Forum Members
Points: 741 Visits: 990
Unfortunately, it will likely be a while from now. I've recently changed jobs and on top of that I am expecting my first child in < 1 month. So, things are busy! But it's still on my radar, just no ETA. For the recent jobs run, you *may* have a process which clears the jobs out of the history tables fairly frequently (I had the same problem on one server I was working with... someone had setup a cleanup process to run every 5 minutes!). You may want to query these tables separately to see what they contain. Let me know if you need help, and thanks for the feedback!
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)

Group: General Forum Members
Points: 741 Visits: 990
For sure. You would need to have all of your linked servers set up correctly, and then from there you could add an input parameter to the proc which would pass the linked server name and append it to the SQL code (some adjustments would need to be made to the code). Or, you could query all of the linked server names from the system tables and loop through, producing a report for each (again, modifications to the code would be needed). Let me know if this all makes sense. Smile
george25
george25
Valued Member
Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)

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

It would be really useful if you could add the path and fiilename of the database and log files to the Database Size (Summary) / Distribution Stats table, e.g. F:\dataorthwind.mdf.

George25
george25
george25
Valued Member
Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)Valued Member (68 reputation)

Group: General Forum Members
Points: 68 Visits: 71
Just read my last post. Not sure what happened to the text but what I wrote got garbled in the translation. What I meant was F:\data\dbname.mdf
Sean Smith (SSC)
Sean Smith (SSC)
Right there with Babe
Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)Right there with Babe (741 reputation)

Group: General Forum Members
Points: 741 Visits: 990
I was thinking of doing that, but I noticed an "issue" with a one-to-many relationship for tables that were partitioned to I opted to leave it out for the first version of the report. I think I will revisit it though. Thanks for the comment. Smile
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