Hi all,
I am using the following connection string in our application (IIS 7, MS SQL Server 2008),
<add connectionString="Server=localhost;Database=XXXXX;User ID=xxxxxx;Password=xxxxx;Trusted_Connection=False;Pooling=true;Connect Timeout=30;" name="LocalSqlServer" providerName="System.Data.SqlClient" />
The database lives the same server as IIS 7.0. The question is about the mechanism that IIS uses to connect to the DB. In particular, I am interested in knowing if it's TCP/IP based vs other (such as shared memory). Is there any way to force IIS NOT TO use TCP/IP given that both DB and application are hosted in the same server? We plan to plug the system in the internet, so if we can guarantee that IIS uses an SQL client provider that doesn't send any packet through the TCP/IP stack, we would increase significantly the security of our application (this is in addition of encrypting the connection string and using a strong ...
Go to the complete details ...