Skip to main content

What is Page File

In short Page File is simply a file on the hard drive that handles situations where the system wants to move or page out sections of memoryThere are several situations that cause this, but the one you're most concerned about is when the system is out of physical memory.Tech net Article is best to configure & monitor Paging File.

A very important question was raised by Parikshit Bisht @ SQLBangalore UG . I am just converting this group discussion into the blog-post, and the Question was as below :  

(1) How we de-fragment page file. 
(2) If my server is 32 bit with 4 GB of RAM. Then what size you suggest me to mention in page file. Same question as regard with 64 bit.
(3) If page file is small size, what problem we face as per SQL Point of view...

Balmukund Lakhani Sir : He said,

Since you have already read many articles, you should know that Page File comes into picture whenever a process data has to be paged out of physical RAM to this physical file.  There are many KB articles on Microsoft site to provide you recommendations. Since you have asked not to paste the link, I would provide KB number 314482 and 889654.Let me attempt to answer the questions now.

1. Here is what I should suggest

a.) Create a temporary page file on another drive
b.) Reboot
c.) Defragment the drive that held the original page file
d.) Eliminate the temporary page file
e.) Recreate the original page file
f.) Reboot
g.) If you want to spend money, Diskeeper is a 3rd party software which does that. (I am not providing any recommendation)

2. Refer the KB which is provided earlier. 

3. Of course, performance hit. If memory page which is SQL data page is paged out, it has be read again from pagefile to memory. 


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription