SQL Jobs are per instance but if you use always on availability groups you can setup a job step to check if this is primary before executing the desired task.

Permissions still active on the sqlJDBCXAUser role?

Hi,

Always held tempdb and logs on the same drive and never found it to have an issue. Although it's always a case of depends.....

One way I've set this up previously is by exporting the job names into a table with a 0/1 in a second column.

That way the table can be updated...

As Krypto said make sure you stop the data transfers.

Also make sure that all permissions are matched through the folder structure.

From 2005 on-wards yes

Yes it's true there's no need to restart the service

https://msdn.microsoft.com/en-GB/library/ms365941.aspx

Although for the agent account on a stand-alone instance of SQL Server, the password takes effect immediately, without restarting...

If you setup always on with a listener you will have a small amount of downtime (milliseconds) when the secondary becomes primary. Most of the time it's not even noticeable.

Hi

Had a similar problem which was caused by inconstant timings with replication at SAN level.

Standard one I've used in the past but you can add extra conditions or use the config file

Sorry hit the wrong slash it should be /q

Setup.exe /q /ACTION=Install /FEATURES=SQL...

Hi Sam,

Not sure if this will be much help - had a similar issue before the following post help diagnose the issue

https://support.microsoft.com/en-us/kb/2001270

Hi,

Looks like it could be a simple as missing out the /q from the command line.

Cheers

Hi,

This is a common issue when the windows installer cache has been cleared.

If you run the installer it will tell you which service packs contain the missing MSI.

Follow the instructions...