hi Barkingdog,

just curiosity- r u generting these number for test data or some kind of data masking.

-- my opinion

it has nothng to do with statistics or restating the server.. its transaction handling issue. logic not written correctly

very interesting.. Here is the challenge to find out what changes could have been done at application side.. definitely its not related to SQL Server settings.

His name is gila and gail <eom>

this has been improved in 2008. Seek happens at partition level and not at total table level.[Partition-Aware Seek Operation]

http://msdn.microsoft.com/en-us/library/ms188279.aspx

why are trying to restore database when log restore is in progress

what is job doing can you provide job details?

you can not back up two databases in a single file.

Are you trying to do this?

there is not rowid equivalent in SQL Server

Please check the the login still exists in the database as a user.

same again.

Log shipping happens at whole database level.. no option to select objects.

Transaction replication facilitates you to select objects and filter the data.

Though there are lots of differences; Major difference is -

Mirroing happens on whole database

In Replication you have option of selecting objects and filtering of data in the publication.

Definitely multiple devices will increase the threads and will do the parallelisim while backing up and restore even if it is on single drive. But if there is bottleneck with...

Wonderful solution Kingston !!!