| Author |
Topic |
|
mfemenel
Professor Frink
1421 Posts |
 Posted - 2002-10-28 : 13:55:13
|
| this is a round about sql server related connection. Our web server is using named pipes to connect to sql. It's crushing our performance on the sql server because each connection is being authenticated. My question is, does anyone know how to change IIS from named pipes to tcp/ip so I can eliminate this as one of our many performance issues? Like I said, sql related in a round about way. Thanks!Mike"oh, that monkey is going to pay" |
|
|
1fred
Posting Yak Master
158 Posts |
Posted - 2002-10-28 : 14:07:08
|
| Under your microsoft sql server group in programs, select client network utility, and just leave TCP/IP in your enable protocol text box. You can leave both but put tcp/ip first if you want it the be the default |
 |
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2002-10-28 : 14:40:33
|
| probably should have mentioned that I already had the sql side set up correctly, but every connection from the web site is still coming through as Named Pipes. TCP/IP is the first default, named pipes, the second. I could disable named pipes completely on the sql server, but my fear is that if I do this, everyone is going to shut down because TCP/IP was first choice and the server didn't choose it.Mike"oh, that monkey is going to pay" |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-10-28 : 14:46:16
|
| Change it using the client Network utility ON the web server.Also this can be set in the ADO connection stringNetwork Library=DBMSSOCNHOWTO: Set the SQL Server Network Library in an ADO Connection String[url]http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q238949[/url]HTHJasper Smith |
|
|
|
mfemenel
Professor Frink
1421 Posts |
Posted - 2002-10-28 : 15:11:09
|
| You may already be a winner.Mike"oh, that monkey is going to pay" |
|
|
|
ksw
Starting Member
24 Posts |
Posted - 2002-10-28 : 17:50:02
|
| Mike,Could you give a little more info on the performance issue you're trying to fix? I have a machine (well 4 actually) that has both IIS & SQL Server on it. I've been tasked with improving performance. What's the difference between Named Pipes & TCP/IP with regards to performance? Does your system setup impact if you should or shouldn't make this change??I'm having a hard time finding info on performance between these two systems so any info you could provide would be greatly appreciated.Thanks,KSW |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-10-28 : 18:33:22
|
| Not regarding this situation specifically but TCP/IP sockets is a less "chatty" protocol than Named Pipes, there's less comunication between cient and server. It has to be said that this is generally not noticeable on a 100MB LAN, it can become apparent on a WAN. Have a look at "Named Pipes vs. TCP/IP Sockets" in BOLHTHJasper Smith |
|
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-10-30 : 14:20:58
|
quote:
I have a machine (well 4 actually) that has both IIS & SQL Server on it.
KSW, I'd give serious consideration to separating your SQL Server instances to a stand-alone machine and not run SQL on the same box as IIS. That way you can configure SQL to maximum capability on the machine, and it won't be slowed down by a bunch of IIS page requests that are trying to be processed at the same time. |
|
|
|
ksw
Starting Member
24 Posts |
Posted - 2002-10-31 : 18:02:08
|
| Jasper, thanks for the info. I'll look that up.AjarnMark, you're the second person that's told me that. Do you have any references I can consult about this, books, websites, whatever? These machines were set up roughly 2 years ago and then there was just one machine so they (these systems are for another department) didn't have any other option but to have both IIS & SQL Server on it. Then as they got new machines to handle the new websites, they just copied the same setup since it seemed to be working. Now we have 3 machines outside our firewall and all talk to the 4th that's inside the firewall. I was asked a month or two ago to help improve the performance of the systems since I'm the DBA on the other SQL Servers that our company uses. I don't know anything about IIS and haven't been able to find any info on the two working together either on the same machine or different ones.I'd really appreciate any help or info that anyone could give.ThanksKSW |
|
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-10-31 : 18:57:07
|
| I have to admit I misread the question, I assumed you were talking about IIS and SQL on separate boxes. By default, local connections between an application and SQL Server 2000 on the same server use the Shared Memory Net-Library which is very fast.The issue with running any application (including IIS) on the same box as SQL is simply a matter of resource contention, mainly CPU and Memory in the case of IIS. Basically you cannot maximise the potential of your server if it's resources are not dedicated to SQL.Depending on the spec of the server and the load on SQL it can be an option but in an ideal world, SQL Servers should be dedicated to SQL.You can check what net library is being used by looking at the net_library column of master.dbo.sysprocesses.HTHJasper SmithEdited by - jasper_smith on 10/31/2002 18:58:15 |
|
|
|
ksw
Starting Member
24 Posts |
Posted - 2002-11-01 : 12:32:02
|
quote:
By default, local connections between an application and SQL Server 2000 on the same server use the Shared Memory Net-Library which is very fast.
Actually, we're running SQL Server 7.0 on Windows NT 4 SP6 on 3 boxes. One box has 7.0 with Windows 2000 SP2. Does that make a difference?--KSW |
|
|
|
ksw
Starting Member
24 Posts |
Posted - 2002-11-01 : 12:46:08
|
| Well I checked our connections, and when IIS talks to the SQL Server on the same box, it's using Named Pipes(SSNMPN70.DLL). When it talks to a different SQL Server inside our firewall (from outside the firewall) it is using TCP/IP (SSMSSO70.DLL).--KSW |
|
|
|
|
IIS Using Named Pipes to SQL