June 15, 2010 at 7:45 am
[font="Verdana"]Hi All,
I have a live/production web application running on IIS and it is using MS SQL Server 2008 and database size around 25GB. Currently IIS & MS SQL Server is running on separate server box and web application is using ADO.NET to connect database server using TCP/IP protocol. Web Application’s connection string having Database Server IP Address. Most web pages having database access of the web application.
My manager (not a DBA) is suggesting me that IIS & SQL should be run on same server box so that the web application will run fast and web pages result fast. Ok! But as DBA I have some questions to myself
How web application will take the advantage to running web & database Server on same server box? After investigation one thing comes in mind that I can use SQL Server Shared Memory Protocol to access database instead of TCP/IP protocol, through web application. So I need to change web application’s connection string and replace SQL Server IP address to (localhost) as described in http://msdn.microsoft.com/en-us/library/ms187662.aspx
Further some more question coming in mind.
1. Is SQL Server Shared Memory Protocol is faster than other SQL Server Network Protocols
2. Is this right way in production environment?
3. Is my database secure from Internet? I will only allow TCP/IP Port 80 & 443 to internet
4. Disaster recovery coming in mind.
So I would like to share this option/solution to DBA Community and request to comment and suggest.[/font]
Ram
MSSQL DBA
June 16, 2010 at 1:28 am
Shared Memory protocol is faster than other protocols. But that should not the only reason for running IIS and SQL Server on the same server.
If the web application is slower, root cause should be found out.
Is your network slower? How about using a faster dedicated network between the SQL Server and IIS server?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply