sorry -- backup log dbname to disk with no_truncate,norecovery

use backup log with no_truncate

which mssql version?

BACKUP LOG database_name TO <backup_device> [WITH { CONTINUE_AFTER_ERROR | NO_TRUNCATE }

backup log not backup database!

select * from msdb..restorehistory

you can script the indexes on one server(db) and run the script inside the other.

yes you can ,change the compatibility when it finish.

Thanks to all!

I succeded to solve the problem using pre-fetch hints .

may you want to see some sample data?

actually I'm interested to rewrite the query avoiding the huge sorts which destroy the performance.

the results are correct

12 rows are returned after 5 hours run.

Hi,

It's a query developped by another and it told me that it returns something.

Hi,

Actually the query run more than 1,5 H and it not g=fiished due the tempdb allocations ,I could isert only estimated exec plan.

Best Regards,

hadrian