Site sponsored by: Idera Try Idera’s new SQL admin toolset
SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Quiz
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

Write for Us

Share you SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

Resource Governor in SQL Server 2008
Tweaks in SQL Server Reporting Services
Configure Filestream in SQL Server 2008
Capture DDL Changes using Change Data Capture with SQL Server 2008 ...

More     
 
Latest FAQ's

SQL Server Reporting Server (SSRS) service is failing to start ...
Cannot Start SQL Server Service
Users are able to connect to report manager but not able ...
Errors when SQL Server Snapshot Replication is Running

More     
   
Latest Software Reviews

Spotlight on ApexSQL Doc 2008
ApexSQL Enforce
Embarcadero Change Manager
SQL Server DBA Dashboard

More     

Is it recommended to install SQL Server on a Windows domain controller?



Question

Is it recommended to install SQL Server on a Windows domain controller? The DC is a Compaq ML 370 2x9Gb(RAID1) + 4x18Gb(RAID5), and is in a remote office supporting 20 users. The DC also doubles as a file server. Any assistance will be greatly appreciated.


Answer

While SQL Server can run on a domain controller, it is not recommended if you are seeking the best performance. For best performance of SQL Server, the server should be dedicated to SQL Server, and not shared with other functions, such as a domain controller or a file server.

It is hard to tune servers that run multiple application, as different application may require mutually exclusive configurations. One example of this is SQL Server running on a file server. For best performance on Windows, the "Maximize data throughput for network applications" option should be selected in order for SQL Server to run optimally. But for file servers, the "Maximize data throughput for file sharing" should be selected for optimal performance. These two settings are mutually exclusive. So if you have a server that is running both SQL Server and acting as a file server, only one of the two can be optimized, and the other one will suffer performance.

Of course, if your SQL Server is not very busy, and you don't ever expect it to be, then sharing server resources can made sense. Only you can decide if compromising SQL Server's performance is the appropriate decision.

Another possible issue with running SQL Server on a domain controller is security. With both running on the same physical server, should one of them be compromised, then is is possible that it might be easier to compromise the other one also.








Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | QDPMA Performance Tuning | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 1999-2008 by T10 Media. All rights reserved