Don't get too jealous, they're Dells!! On 17 June 2010 00:00, Ziots, Edward <ezi...@lifespan.org> wrote:
> I cant see 256GB of RAM getting filled in a SQL 2005 X64 Setup anytime > soon, especially if you cap the memory via SQL Studio. Are you clustering > this and going with multiple SQL Instances or just 2 separate boxes, and a > Mirroring setup? Paging (little if at all) should be like the last thing > you should be seeing from those monster type boxes. And I though systems > with 32GB of RAM these days was sick… > > > > Z > > > > Edward Ziots > > CISSP,MCSA,MCP+I,Security +,Network +,CCA > > Network Engineer > > Lifespan Organization > > 401-639-3505 > > ezi...@lifespan.org > > > > *From:* Jim Holmgren [mailto:jholmg...@xlhealth.com] > *Sent:* Wednesday, June 16, 2010 10:36 AM > *To:* NT System Admin Issues > *Subject:* Disable paging file? > > > > Hey folks, > > Looking for thoughts/experience/opinions on paging file usage on systems > with large amounts of RAM. Primary application will be SQL Server 2005. > > We have a pair of new Dell R910 servers, each has 256GB of RAM. The > default swap file created by Win2008 R2 Enterprise basically filled ¾ of > the local storage that we bought with the server (primary storage will be > SSD drives on our CX4 array). > > We’ve been kicking around the idea of either: disabling the swap file > altogether, forcing it to something smaller, or purchasing some additional > local storage to dedicate to swap. > > I’m concerned with application crashing if/when memory gets filled and has > no swap to move to – but at the same time, it’s 256GB of RAM – should take > quite a bit to fill. Right now, I’m leaning toward buying some additional > local storage and dedicating it to swap. Seems like a waste of resources, > but this is an essential business application so money is easier to come > by for this. > > Interested in hearing your thoughts or experiences. > > Jim > > Jim Holmgren > > Manager of Server Engineering > > XLHealth Corporation > > The Warehouse at Camden Yards > > 351 West Camden Street, Suite 100 > > Baltimore, MD 21201 > > 410.625.2200 (main) > > 443.524.8573 (direct) > > 443-506.2400 (cell) > > www.xlhealth.com > > > > > > > CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole > use of the intended recipient(s) and may contain confidential and/or > protected health information. Under the Federal Law (HIPAA), the intended > recipient is obligated to keep this information secure and confidential. Any > disclosure to third parties without authorization from the member of as > permitted by law is prohibited and punishable under Federal Law. If you are > not the intended recipient, please contact the sender by reply e-mail and > destroy all copies of the original message. > > NOTA DE CONFIDENCIALIDAD: Este mensaje incluyendo cualquier anejo es para > uso exclusivo del (los) destinatario (s) y puede incluir información > confidencial y/o información de salud protegida. La Ley Federal (HIPAA) > establece que el destinatario está obligado a mantener la información > confidencial y sequra. HIPAA prohíbe y castiga cualquier divulgación a > terceras personas sin autorización del afiliado o permitido por ley. Si > usted no es el destinatario, redirija esta mensaje al remitente, y destruye > cualquier copia existente del mensaje original. > > > > > > -- Kind regards, Andrew Levicki MCITP:EDST7/EMA/EA,MCSE,MCSA,MCP,CCNA,ITIL ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
