|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, September 20, 2012 1:35 AM
Points: 133,
Visits: 280
|
|
| An easier way to distribute monitoring jobs is to use the master and target feature that way you can implement all your jobs or maintenance plans on a central server which then distributes and controls the jobs even holding the logs centrally and this way you are gurenteed that all monitoring jobs on each server are exactly the same so no inconsistencies creep in.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:11 AM
Points: 409,
Visits: 408
|
|
I have already implemented such a design in my place. I believe much better to achieve the same is using the powershell, where you no need to create the linked server, as linked servers sometime can cause performance issues. Powershell is the best way to achieve the same.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, September 20, 2012 1:35 AM
Points: 133,
Visits: 280
|
|
| Is that only in SQL 2008 though? It would interesting to hear more about this, there seems to be so many different ways now, especially with 2008, to administer SQL accross a few servers that it's really becoming an art in itself, which one is best? I've tried several different approaches but am still unsure that my master target method in 2005 is the best, it's certainly best for keeping it consistent but what is more efficient?
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:11 AM
Points: 409,
Visits: 408
|
|
| No need to have 2008. We can install on one server and can remotely access the data from the client server.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:11 AM
Points: 409,
Visits: 408
|
|
here is one link
http://www.simple-talk.com/sql/database-administration/why-this-sql-server-dba-is-learning-powershell/
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 2:11 AM
Points: 409,
Visits: 408
|
|
Using the linked server concept, we also need to load the ole's in sql server to get the clients disk space data. using the power shell, its quite simple.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, September 20, 2012 1:35 AM
Points: 133,
Visits: 280
|
|
| I read the article and it was very useful, some of the things like running queries accross multiple servers can now be done in SQL 2008 and some of the other tasks I could think of better ways to retrieve the information like disk space but for finding out Windows information I should think this is very useful, if I can't get our monitoring tool to pick up information from the event viewer I will look into this as a way of getting this.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, November 22, 2012 1:35 AM
Points: 23,
Visits: 168
|
|
I have done a similar thing with SSIS, you just need to add the new monitored instance into a table in your repository and ensure the account running the package has permission on the target Instances. I then have 3 packages, one that runs stat's daily, one that runs hourly and one that checks status, agent heart beat, PLE etc every 5 minutes. I then have a aspx page looking at the repository for status info and some reporting services reports pulling of trend graphs etc.
I beleive i got the original SSIS packages from a feature on this site and modified it to add more metrics and update the code for SQL 2008 instances.
Cheers, Paul
|
|
|
|