Home > database >  MSSQL backup reduction, speed did not improve
MSSQL backup reduction, speed did not improve

Time:09-22

Have A A server (compared with the old, poor performance), used to install, because the CPU is always to 100% last year, will be moved to B after A full backup database server (good) performance, after initially loaded on the client connect to the database, query speed quickly, but after the 4/5 months, slowly again,

Yesterday we continue to B server database backup, and will be retained after the original database rename bak, and also in B to restore the database server,
But after the client connection, found that the system has not changed quickly,

Clearly the same operation, and last year are backup restore, why didn't achieve the result that as same as last year?

Guess: when reduction last year, has been put into the database on the server at the early stage of the (test), and installed in the default location, reduction, overwrite directly, this year did not cover the original database, and is not installed in the default location (in E disk DATA folder, MDF and LDF change to E disk)

  • Related