Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server on Domain Controller Expand / Collapse
Author
Message
Posted Tuesday, April 13, 2010 10:58 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, March 31, 2012 3:12 AM
Points: 6, Visits: 221
Hi friends

Well, i have been told to never install a sql server instance on a windows server domain controller, but nobody cared to explain why is it so..
Can any of you folks tell me any proper reasons for the same...or atleast provide links to any suitable articles??
thanks...
Post #902875
Posted Wednesday, April 14, 2010 5:03 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, November 21, 2014 2:25 AM
Points: 364, Visits: 1,331
Microsoft recommends to "isolate services", see http://msdn.microsoft.com/en-us/library/ms144228(SQL.90).aspx
I have some experience in running a SQL 2005 instance on a domain controller. The MSSQLSERVER service ran on a domain account. When applying SP2, I had a problem that I described here: http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/061b2f31-7cf2-4ff3-a582-6d7d01224156/?prof=required&wa=wsignin1.0.
However I do not think that this happened because the machine was a DC.

Post #903001
Posted Thursday, April 15, 2010 3:54 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
As per http://www.sql-server-performance.com/faq/domain_controller_performance_p1.aspx

1.

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.


2.

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.

MJ
Post #904456
Posted Thursday, April 15, 2010 4:27 PM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 12:51 PM
Points: 17,948, Visits: 15,948
It is possible (Small Business Server does the same sort of thing), but I would never do it.

Why? Same reasons as already listed.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #904468
Posted Friday, April 16, 2010 6:11 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 3:49 AM
Points: 1,622, Visits: 5,695
I suppose it depends to an extent on the size of the domain. If you have a domain controller which is only servicing a few dozen users then it's under practically no load anyway, so using it as a SQL server isn't going to cause an issue. If your domain controllers are servicing thousands of requests then it obviously gets trickier!
Post #904758
Posted Friday, April 16, 2010 8:37 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 12:51 PM
Points: 17,948, Visits: 15,948
Another consideration is along the lines of security. If your DBA needs access to the server and you have them combined with the domain controller, you have a precarious situation. Do you want a DBA touching a Domain controller? The situation is of little concern if it is a one-man shop, but it doesn't resolve the need to be extra cautious when securing both the database server and domain controller while not breaking the other.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #904906
Posted Monday, October 8, 2012 2:29 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, February 1, 2013 2:53 AM
Points: 2, Visits: 6
Hi All,

I know it is post on outdated post but I have a little query regarding the DC and DB server setting in the network.

At one of the client place we are facing a very slow ms-sql 2008 access when > 50 users are working. The application is .net application.
The configuration is as follows.
1. Data server xeon processor (2 processors) with 32 GB RAM
2. 600 GB SAS harddisk
3. MS-SQL 2008
4. Windows 2008 R2 OS
The network is local area network and is security is controlled by a domain controller which is not in the same network but is remotely(internet) located in another location (4 Mbps) dedicated lease line.

I think the DC authentication while accessing the DB will make it to run slow. Please guide.
Post #1370042
Posted Monday, October 8, 2012 3:33 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:07 PM
Points: 6,626, Visits: 14,196
Quite right, SBS runs Exchange, SQL server, IIS and domain controller. Its mainly about performance, which is why the min spec for an SBS server is so high for such a small number of users

Security is also a factor too.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1370087
Posted Monday, October 8, 2012 10:39 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, February 1, 2013 2:53 AM
Points: 2, Visits: 6
Hello,

Application
In this case we have a Hybrid application accessing same dataabase.

For local area network- Windows application
for web - Web application

Servers
IIS server - Application (server 1) 60-70 web users currently
DB server - Data base (server 2)
Exchange server - exchange (server 3) 200 users

My main concern is that DC is not in local area network (It is remote). Do you think that DC (connected via 4Mbps lease line) is the bottleneck for running slow quaries the SQL server.

Kamal
Post #1370158
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse