March 6, 2007 at 12:32 pm
This is probably naive, but what does SQL Server consider to be a remote connection? Anything that doesn't connect via shared memory?
Is there a way to have a .Net application (using IIS) connect to SQL Server via a local connection? Am I crazy for even wondering about this?
Currently, we are using SSPI in our connection string which connects through TCP/IP...
Thanks,
Michael
March 6, 2007 at 2:11 pm
My SQL Server is in my box so that is local connection but through the new surface area configuration tool you can enable both local and remote. And if SQL Server is some where in the network then you need to enable the browser service which is for remote connection. If you have SQL Server installed click on configuration, if not run a search for surface area configuration in SQL Server BOL(books online). Hope this helps.
Kind regards,
Gift Peddie
March 6, 2007 at 2:49 pm
IIS and SQL Server are on the same physical machine, and the IIS process user has an appropriate login to SQL Server - this is using SSPI. For this to work, I have remote connections enabled since this uses TCP/IP. However, is there a way, even using something other than SSPI, that IIS can connect to SQL Server through a local connection? I am new to this...
March 6, 2007 at 3:32 pm
Try the link below for many connectionstring options.
http://www.connectionstrings.com/
Kind regards,
Gift Peddie
March 6, 2007 at 5:33 pm
Yes, I have enjoyed that site thoroughly and that is where I double-checked my SSPI connection string. However, it doesn't answer my main concept question as to whether IIS can connect to SQL server through "local" means or whether any such connection will be considered remote.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply