I'm a fan of A where possible. In your scenario you can probably get away with one server with CF + MSSQL for a while and move the separate DB to your scalability plan. But you should carefully tune the CF heap and memory limit of SQL server to make sure that each of them uses only X amount of memory. If you don't, SQL server will expand to use up all available memory and when your heap needs to reszie you may get an outofmemory error. But most folks forget that SQL can be fine tuned to use only a certain amount of physical memory. You should also disable Named pipes and shared memory libraries - leaving ONLY tcp/ip as the net library of choice for DB access. Disable all uneeded services and exclude DB folders from AV scanning. That's my 2 cents
(hey Kelly :) -----Original Message----- From: Kelly Matthews [mailto:ke...@webdiva.org] Sent: Friday, January 14, 2011 8:45 AM To: cf-talk Subject: Re: (ot) Server Setup Opinions I'd go with option A. The one time I had SQL and CF on the same box it caused issues and was not efficient. >No problem. Were a Windows shop. So it will be Microsoft 2008 R2 for the OS >and the DB. > >Oops sorry for the dupe. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:340868 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
