November 2, 2007 at 5:40 am
Hi all,
I have 10 servers and i want to implement this concept for any job failure and checking the disk space and transaction log size.
I want to use a single code or program for getting above details in a shot in excel sheets. currently for job failure i am using two sp's which executes every 2 hours on a day basis and send me an email for any job failure. for this i copy these two sp on every server but i want to know how to achive other tasks, is there any other tool or any concept of doing the same.
Thanks & Regards
shashi kant chauhan
November 2, 2007 at 7:12 am
write a TSQL code to accomplish the job failure details your disk space and tlog space. Then i would suggest as given below.
1. create a .cmd file
2. place the cod given below in the cmd file
osql -E -Sservername -i \\drive\sql.sql -o \\drive\output.xls -n
osql -E -Sservername -i \\drive\sql.sql -o \\drive\output.xls
replace the server name parameter.
hope this helps.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
November 2, 2007 at 12:41 pm
Another option (one I'm using) is to store your data in a table on each server. Then write an SSIS package to collect (and possibly condense) the data onto a single server into a summary table. Then lastly write another SSIS (or add to the end of the first one) to export the data into your Excel spreadsheet.
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
November 4, 2007 at 10:09 am
I've done something similar to what Kenneth suggested.
Have each server monitor itself. That way if your central server is down or there's some issue, the reporting still runs.
I used to make a small db on each server, that way it's standard, and use tables to store the info. USe a separate table for each, then I'd create a central reporting table and populate that with a local job that shows the data for the day (or period). That way you can quickly pull the data off that machine if necessary.
After that, I'd have one server roll everything up and it should know which servers it's pulling data from. If there's no data, be sure to flag that and then export to Excel.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply