Link to home
Start Free TrialLog in
Avatar of info2rafiq
info2rafiq

asked on

Why OS Paging is high while restoring database in SQL Server?

Server Configuration:
1. Windows 2003 Enterprise X64 SP2
2. 4 dual core processor
3. 32 GB RAM
4. Page file size: 48GB
SQL has been allocated 26 GB of RAM as MIN and MAX server memory. Lock pages in memory is already enabled for the SQL account. Backup file size is around 30GB and stays in a different server. The moment restore starts, OS paging goes high as above 5000 with high page faults/sec and cache fault/sec. Page file usage never goes beyond 2%. Available MBytes dips only a few MBs, say 9-12MB as noticed. SQL Server working set size also remains same, but the procedure cache dips as long the restore operation goes and jumps back to normal immediately after restore is done. Disk is not a bottlenect which has already been identified.
Can anyone help me understand why is it happening with the solution?
Avatar of Guy Hengel [angelIII / a3]
Guy Hengel [angelIII / a3]
Flag of Luxembourg image

>Backup file size is around 30GB and stays in a different server
this is the key. the restore has to read the file remotely, while doing the restore.
better would be to have the file copied locally, and doing the restore from there.
Avatar of info2rafiq
info2rafiq

ASKER

My environment doesn't permit to copy the file locally. Is there any other alternative that we can think of?
the only alternative would be to restore on another server, detach there, copy/move the .mdf/.ldf to this server, and attach ...
Is there anything about the NIC drivers that we could think of upgrade? We are using Broadcom Xtreme Giganet drivers in our environment. Also does TCPChimneyOffset play any role into this?
ASKER CERTIFIED SOLUTION
Avatar of Guy Hengel [angelIII / a3]
Guy Hengel [angelIII / a3]
Flag of Luxembourg image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial