InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 08:53:51 GMT20http://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxHello,[u][b]Application[/b][/u]In this case we have a Hybrid application accessing same dataabase.For local area network- Windows application for web - Web application[u][b]Servers[/b][/u]IIS server - Application (server 1) 60-70 web users currently DB server - Data base (server 2) Exchange server - exchange (server 3) 200 usersMy 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.KamalMon, 08 Oct 2012 22:39:07 GMTkamal-624511http://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxQuite 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.Mon, 08 Oct 2012 15:33:51 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxHi 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 RAM2. 600 GB SAS harddisk3. MS-SQL 20084. Windows 2008 R2 OSThe 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.Mon, 08 Oct 2012 14:29:14 GMTkamal-624511http://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxAnother 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.Fri, 16 Apr 2010 08:37:31 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxI 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!Fri, 16 Apr 2010 06:11:46 GMTpaul.knibbshttp://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxIt is possible (Small Business Server does the same sort of thing), but I would never do it.Why? Same reasons as already listed.Thu, 15 Apr 2010 16:27:10 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxAs per http://www.sql-server-performance.com/faq/domain_controller_performance_p1.aspx1.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.MJThu, 15 Apr 2010 15:54:16 GMTMANU-J.http://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxMicrosoft recommends to "isolate services", see http://msdn.microsoft.com/en-us/library/ms144228(SQL.90).aspxI 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.Wed, 14 Apr 2010 05:03:18 GMTdmoldovanhttp://www.sqlservercentral.com/Forums/Topic902875-146-1.aspxHi friendsWell, 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...Tue, 13 Apr 2010 22:58:08 GMTssdba