from the BOL looks like its supported. Did you try it ?

thanks very helpful

don't need to change the the umber , its for internal microsoft use only.

if you look down the script for that entry the number has already been changed for you

hyper-v with sql server 2005 on a windows 2008.its now supported by Microsoft

Elliot , its not a question of being paranoid or that the structure of the restore may be corrupt. Its more about complying with the sql server checksum page...

thanks gail , that makes sense , i assume the bit about forcing the checksum on all the pages by creating the clustered index where not present and re-

building...

Yes , just re-booted the sql server instance, i did not re-boot the windows server

ok , the server in question was a production server for us, i rebooted the sql server on the windows server around 10pm when we have nothing running on...

Got exactly the same issue, don't understand why it would go tiz like that. I've checked the plan databases via checkdb etc and backed up manually using the verify option....

thank u

actually its one i inherited , I'm thinking about changing it to a standby but wanted to know if i could do it without changing the log shipping ...

thanks ....

thank you ...