Monday, March 12, 2012
MS SQL Jobs
I am trying to run a job on Multiple SQL Servers in a domain.I am setting the job on my system,but the Radio button "Target Multiple Servers" is disabled.How do I enable the radio button "Target Multiple Servers".
Please let me know if this is possible.
Best Regards
SK.you have to ensure that your machine is a master and that you have
registered servers to be targets.
Right click sql server agent -- Multi Server Administration -- Make this a master.
During this process you will be asked to create a MSX operator. and to enlist targets. the targets will need to be pre-registered with your master's instance and then define the jobs on the master and then you will be able to target multiple servers.
understand that this process is designed to return all job history to the master so you can check the progress of job operations from one place. however, just as with the highlander, there can be only one.... meaning that a target cannot be a master for other servers.
:confused: and dont forget to check books online,
BOOKS ONLINE {Multiserver Administration}
Wednesday, March 7, 2012
MS SQL 2005: DB Mirroring and Log Shipping
However I am running into a bit of a snag in configuring the mirror as the primary/inactive log shipped database.
From what I can tell one should be able to configure the mirror DB separately as a logged shipped database and when a mirror failover event happens the Log Shipping jobs should be able to come from whichever is the active DB.
According to all the documentation I have it is possible, however it is a bit fuzzy on the details. Is this a MS pipedream or Reality? Has anyone accomplished this?
Your input?I was able to figure it out.
Here is my solution. I welcome your comments.
Prerequistes: Mirroring Endpoints, 3/4 servers (primary/mirror/logship/Logship backup servers), SQL Server 2005
1. create a backup of the database to be mirrored logshipped
2. copy backup to both mirror server and log ship server
3. recover backup fully on mirror server
4. set up log shipping on the mirror server (initially disable backup job)
5. re-recover database in NORecovery mode
6. point mirror database at primary database
7. set up log shipping on the primary server (initially disable backup job)
8. re-recover database on primary database (Key! - I'm not sure why however)
9. point primary database to mirror database to initalize DB mirroring (also may setup a witness at this point)
10. setup log shipping on log ship server (initially disable copy and restore jobs)
11. ensure that all settings are working correctly and DB Mirroring is fully functional
12. Enable backup jobs and then copy and restore jobs for Log Shipping
What this accomplishes is a Mirrored database which also log ships from two locations (both the primary and the mirror db). Upon a mirror failover event the Mirror DB will continue logshipping
I am still testing this solution. Hopefull you can make some use of this information.