SQL Best Practices: Dedicated Hardware


 

can point me ms best practices advise against installing non-sql-related applications on sql db server?  feel common sense have been asked justify direct statement microsoft.  help?

i don't think find such statement microsoft. potentially alienate many isv's products might designed operate on 'only' server small organization might possess. in fact, microsoft's own windows small business server allows installing both sql server , exchange on a server domain controller , file server.

 

however, following 'rule of thumb' of adhere to: if data server 'mission critical' foolish try save few dollars @ potential cost of slower response, , or total disruption of server caused uses other data needs.

 

sql server designed use processors , memory on server. will, grudgingly, cede cpu cycles , memory demands placed on os other applications.

 

i have clients using virtural server (to isolate sql server) on multi-processor servers, other critical applications using separate virtural machines. in scenario, each vs/vm gets own dedicated cpu/memory resources , not have 'share'.

 



SQL Server  >  Getting started with SQL Server



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........