InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 22 May 2013 03:09:31 GMT20http://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxfor us, we use an MSX server. each set of servers in that cluster or the target of replication get pushed those jobs hosted at the MSX server level. When a change to that job is made, it pushes it to all boxes it's targeting. That might be what you're wanting. we use this on clustered and transaction replication based setups. (as well as all other servers). so not exactly a fail over item, but it would qualify as a failover solution.Tue, 12 Mar 2013 12:02:18 GMTBill (fluffydeadangel)http://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxWell I didn't say run them manually...If you want server 4 to be able to run server 3's jobs when server 3 fails, then you need to have those jobs on server 4. Since MSDB is a system database and written to by SQL Agent, that can't be via mirroring, log shipping or availability groups. Perhaps replication, I can't recall offhand whether MSDB can be published.Then you either need to ensure that SQL Agent on server 4 is stopped and manually started when server 3 goes down, bit of a pain there, or have something in the jobs, probably as the first step, that checks what server they're on and what servers are active and online to see if they should run. So jobs on server 4 check to see what server they're running on, see server 4, then check whether server 3 is available, if it's not run.Mon, 11 Mar 2013 08:05:51 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxU mean to say that we need keep the same Jobs in third server and run it manual when fourth server is goes downMon, 11 Mar 2013 07:15:28 GMTratheesh4sqlhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxSyncing the jobs is the easy part, just copy them to the other servers. You just need some check in the job to ensure that it won't run on the secondary if the secondary is inactiveMon, 11 Mar 2013 06:32:40 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxJust the jobs? What about the databases those jobs connect to? What HA/DR do they have set up?Yes..i have setup database level HA in four servers using sql always ON. The Fourth secondary server i have created number jobs pointing to the listener IP. here is any possibilities to fail over jobs to third server if there any issue comes in fourth server ?Mon, 11 Mar 2013 06:30:29 GMTratheesh4sqlhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxJust the jobs? What about the databases those jobs connect to? What HA/DR do they have set up?Mon, 11 Mar 2013 06:16:42 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxI am looking for solution to fail over my scheduled jobs to the different server when if there is any issue comes job server....because its very critical jobsMon, 11 Mar 2013 06:05:01 GMTratheesh4sqlhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxCould you be more specific? Fail over when, to what, etc.Mon, 11 Mar 2013 05:49:34 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1429193-2799-1.aspxHi,Is there any possibilities for SQL server Job fail over to the different server???Mon, 11 Mar 2013 05:41:57 GMTratheesh4sql