8 hours is way over the top, take a look through the errorlog to see which parts took so long. I am not aware of any OS dependencies or bugs...

this is normal behaviour and hopefully upgrade script mode has completed by now.

the last phase of patching a SQL2008+ cluster node is to fail over to the node, at that...

same process but what are you aiming to acheive here? If the secondary is...

http://msdn.microsoft.com/en-us/library/aa496029(v=sql.80).aspx

do you mean backup across the network? If so yes that is possible so long as SQL is running under a domain account and you have the permissions set up...

the principal and process for log shipping was the same in SQL2000 but the set up gui was different. It was also only available in the enterprise edition.

If you have...

Always best to.

Does the advisor has to be...

if it is a side by side upgrade check the database owner is still what you want.

other than that thats all that is required as part of the process, I...

for system databases see here

make sure you use the procedure for your version of SQL (I have presumed 2008)

I would guess there was more work for the reindex to do this time, it then became a timing issue as it ran into your online day.

running this daily is...

either dive down and get it 🙂

or

if logs wont load because of missing lsn restart from a full again or if you have not taken a full backup of the...

vishalsurya50 (3/15/2013)

---

Normally what are the causes for this type of long running re-index query ?It ran for 7 hrs.. normally it would run within 5 mins. I checked sp_who2...

which step ran long?

If the reindex step does the reindex depend on thresholds to determine what it reindexes or always reindex everything?

any output from the job?

as anthony said but I would stop the apps first and take backups of all the databases.

also, are you moving just user databases or system databases as well?

Tripz (3/14/2013)

---

To avoid all the confusions and complications

I created a fresh db on dev and restored the backup to this freshly created db.

and now things seems to be clean...