if copy the statement in restorelog job to a query window and execute you may get detailed information.

if you declare your cursor as insensitive then you wouldnt get this error.

we have same issue, it happens sometimes because the disk which snapshot files resides becomes full. there are case that we have plenty of space again it is marked suspect....

hi,

-move your logins to newly installed cluster sql server database.( better to get the login scripts and run after moving db(s))

-convert your dts's to ssis and deploy them to cluster...

if your log backups are not compressed then it would be ok. but if you are using compressed backups then you should use compressed_backup_size field.

we had the same error messages while querying table having computed columns but after collecting statistics and update usage no more errors appear in the log.

stats seems to be stale. auto stats wasnot ON for that table. gathering index solved our case. thank you

it is a single query from a third party application.for different dates a can see the full query and completes in 5 secs.

we are using a view joing all user database sysobjects. it may be a start.

restore database Db_name from disk ='path' with norecovery

go

restore log db_name from disk='path\log1' with norecovery;

go

restore log db_name from disk='path\lastlog' with recovery ,stopat='timestamp';

go

in this case SQL server works just like Oracle, restore Full backup and then TRN log until the point where you dropped the table ( using stopat=timestamp)

GilaMonster is right you have to wait till it completes.

Check if firewall is OFF in both servers. IF your OS is Windows 2008 it comes with firewall ON

you can also check application eventviewer logs.

As far as I know mirroring configuration must be done with hostnames. add those IPs to host file and use their hostnames.