I don't type as much as I cut and paste or load pre-written scripts, most frequent of those would be to show fragmentation on all indexes and reverse engineer database...

the install process (add node) puts a copy of the resource database on each node. It is considered to be the same as any of the .exes or .dlls as...

the resource database should be on a local drive, leave it where it is.

Antonio,

have you tried the query I posted?

you don't need a monitor, the table is in msdb.

Another option would be to rebuild your system databases to get you back to your vanilla installation (presuming this is not a prod server with other amendments)

https://msdn.microsoft.com/en-us/library/dd207003(v=sql.105).aspx

the extra objects in...

check the SQL errorlog, and see what this query returns

select log_time_utc,message from msdb.dbo.log_shipping_monitor_error_detail

We generally stick to SPs. Way too onerous and too many outages to keep up with CUs.

for a new system from scratch could start with the latest (or near latest)...

the move is as for a standalone server.

No need to reboot anything, just offline\online the SQL resource via failover cluster manager

as ever, excellent perry

ask them how they would fail over a mirrored database manually, there are two main commands and hopefully they would say if possible they would ensure the mirroring was in...

it will be spread across the files, distribution depending on their size and free space.

IIRC if you perform the restore via the GUI you can also script it out.

Be careful if you are using logshipping, you don't want to have log backups outside the jobs that are part of logshipping.

I would approach it differently, either build sp_start_job commands...

SQL service packs are cumulative so you are on the right track. However a service pack will probably not contain ALL CUs from the previous SP, as the code will...