July 7, 2010 at 9:43 am
Hi,
We run maintainence tasks on all our servers, some are daily, some are weekly.
What i need to do is :-
1. capture the 'messages/result' that is thrown by these maintainence tasks into a temp table.
2. A job will push the records from the temp table to a centralized server.
3. Centralized server will read the records, will create a mail for servers which had issues/errors and will e-mail the details to a designated list of sysadmins. 1 mail per job.
Step 2 and 3 are ok as of now.
I need help in step 1. Basically i have these jobs that are scheduled on the servers:
1. check disk space (hourly)
2. Check File group usage (hourly)
3. Cleanup disk (hourly)
4. Archivelog (daily)
5. Litespeed backup full (daily)
6. reindex/reorg (weekly)
7. update stats (daily)
8. check blocks (5 mins)
These jobs are running fine as of now. I need to capture the output of these jobs (including detailed messages) into a temp table.
1. What structure should be best for this table?
2. How can i capture the messages and store in the table?
I need to store these columns with all records: servername, instancename, date/time(getdate()), row number(auto increment), job name, message_line_no (if messages are spread across multiple lines, and message itself.
Any input in the right direction will be highly appreciated.
July 7, 2010 at 11:05 am
ps. (7/7/2010)
These jobs are running fine as of now. I need to capture the output of these jobs (including detailed messages) into a temp table.1. What structure should be best for this table?
Post suggest that needed information is: servername, instancename, date/time(getdate()), row number(auto increment), job name, message_line_no (if messages are spread across multiple lines, and message itself so - there is the basic structure of the table.
ps. (7/7/2010)
2. How can i capture the messages and store in the table?
"insert into" would do.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply