SQL Server Install Without OS Page File
What is the impact, advantage or disadvantage when installing SQL Server on a windows machine that does not have a swap file for virtual memory?
When optimizing a SQL Server, one of the things you audit is the weight of paging, swapping memory to disk to make room for other work, to determine if you have adequate memory for the load on a SQL Server.
If you have no page file, you have no virtual memory paging. This results in blocking instead. As a result you are aware that you are under stress for inadequate memory, which is what you should address with paging or without.
Is this a technique you consider viable? What other considerations should be considered prior to this configuration? Would you make a different configuration if the server was not providing the single purpose of SQL Server?
Feel free to drop me a note at btaylor@sswug.org if you would like to contribute to the conversation.
Cheers,
Ben
JSON Comments
Ian Writes:
JSON’s reduced verbosity advantage is only significant when compared with XML that uses elements for property storage; if one uses attributes rather than elements for properties, then the advantage is insignificant, especially where the data payload is significant.
The problem is that most "XML" used for data transfers either isn’t efficient (over-verbose) or isn’t XML at all, just a collection of open and close tags upon which a schema simply can’t be built!
–
$$SWYNK$$
Featured Article(s)
The Secret behind Accurate Estimating (Part 3)
This series covers three methods of charting and logging your work product estimations: Iterative charting to improve accuracy, charting for effective communications and charting for a streamlining process example.
Featured White Paper(s)
How to Implement an Effective SharePoint Governance Plan
Written by AvePoint
Moving past the "what" and "why" of governance, an even… (read more)