As per this DMA document link, its showing backup and restore will work for SQL 2008 SP2 to SQL 2017 without updating SP4.

Backup and restore: A backup taken on SQL...

You can reduce the backup time by specifying multiple files instead of single file. Or try with Blocksize=65536 if you are using single device

i can see low PagelifeExpectancy and high pages/sec showing memory issue..

I like the step by step approach for learners...

MAK

looking forward to the next part.. you have selected the very important topic for all dbas...

check this out

i remember the query optimization stuff gail mentioned about can be found in the book "SQL Server Query Performance Tuning Distilled by sajal dam"

take a look at the pagelifeexpectancy counter, it should not be less than 300 , it it is very low

you cache is clearning frequently because of less memory.

Did you monitor the memory counters that time? Is there any memory pressure?

monitor SQLServerBufferManager counters Buffercachehitratio, Pagelifeexpectancy

etc and find any major differences.

run profiler(filter using db_id ) to find the activity going on to that database

drop and recreate the index for the table id -2321667210 and run dbcc again

Rough estimate is 25% of your big database size. You can estimate the dbcc checkdb tempdb requirement by running DBCC CHECKDB WITH ESTIMATEONLY. Temdb growth depends on how many worktables/objects...

Consider removing the Windows NT Boost Fibers option & verify the indexes, fillfactor to improve data loading

I agree with Rudy, I had the same problem too because of the network. I defect all the servers and enlisted again. I could not able to enlist the target...

i have more than 100 servers running with MSX-TSX relationship, works fine. All the remote server maintenance jobs are created on the MSX are downloaded by the TSX with in...

EM does'nt support Restore with Password