doesn't matter, you can switch between modes.

Thats correct, restore the full backup and any differentials...

SQL Server MVP deep dives (various)

Really 🙂

If you only need data on the reporting server nightly have you considered log shipping? Just hold off on the restores during the day and have the database in standby\read...

you can upgrade just one instance.

In this case I would recommend doing the upgrade manually.

you cannot do a log backup on the master database as it can only be in simple mode. That will be why the TLOG backup is failing for system databases...

hard to say on index rebuilds, check the fragmentation daily to see how quickly the indexes fragment.

You may want to update your stats after the upload though. Presuming you have...

So when you finish for the day you shut down SQL? If this is just to record that then how are you shutting down SQL?

If just through the services applet,...

of course, if your aim is to save typing, rather than

EXECUTE sys.sp_configure

@configname = 'show advanced options'

,@configvalue = 1

type

exec sp_configure 'show advanced...

no probs. Eddie Vedder is it?

I doubt those two events are related. Sounds like something has happened to your account in AD (maybe recreated) so it no longer matches to the SID SQL holds for...

no, that information is not kept in the msdb database.

the only thing that would revert the settings is restoring from a backup of the database before the change.

recovery time is adversely affected by large number of vlfs in a transaction log file (see here)

so it is worth checking your databases for this condition (rule of thumb. vlfs...

yep, thats the classic cause of that type of error in logshipping.

glad you sorted it.