| Groups | Blog | Home |
sql server connect : Named pipes causes intermittent freezing !
a SQL 7 server (running on NT4). This was causing a periodic "freezing" in our application whereby all connections to SQL were made to wait around 30 seconds - even with just one user connected. (Our application accesses SQL via ADO). We went in and changed all the clients to use TCP/IP in cliconfg and the problem seemed to be fixed. However, no-one seems to have a clue as to why, including me - can anyone understand this, or even suggest a possible reason? Thanks, Robert Steadman Vebra
trusted or sql standard login?
-- Kevin Connell, MCDBA -------------------------------------------------- The views expressed here are my own and not of my employer. ---------------------------------------------------- [quoted text, click to view] "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message news:OpjBmStnDHA.2732@TK2MSFTNGP11.phx.gbl... > We have a customer setup where all users were connecting via Named Pipes to > a SQL 7 server (running on NT4). This was causing a periodic "freezing" in > our application whereby all connections to SQL were made to wait around 30 > seconds - even with just one user connected. (Our application accesses SQL > via ADO). > > We went in and changed all the clients to use TCP/IP in cliconfg and the > problem seemed to be fixed. However, no-one seems to have a clue as to why, > including me - can anyone understand this, or even suggest a possible > reason? > > Thanks, > Robert Steadman > Vebra > >
The reason I ask is because if you are using named pipes with sql logins,
you may be still be doing NT authentication. I've seen situations where authentication became delayed. When you say "freezing" do you mean new connections could not be made, or existing connections could not do work, or both? -- Kevin Connell, MCDBA -------------------------------------------------- The views expressed here are my own and not of my employer. ---------------------------------------------------- [quoted text, click to view] "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message news:##k7hK5nDHA.1004@TK2MSFTNGP09.phx.gbl... > All SQL logins. > > "Kevin" <ReplyTo@Newsgroups.only> wrote in message > news:%230Kh9oxnDHA.1740@TK2MSFTNGP12.phx.gbl... > > trusted or sql standard login? > > > > > > -- > > Kevin Connell, MCDBA > > -------------------------------------------------- > > The views expressed here are my own > > and not of my employer. > > ---------------------------------------------------- > > "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message > > news:OpjBmStnDHA.2732@TK2MSFTNGP11.phx.gbl... > > > We have a customer setup where all users were connecting via Named Pipes > > to > > > a SQL 7 server (running on NT4). This was causing a periodic "freezing" > in > > > our application whereby all connections to SQL were made to wait around > 30 > > > seconds - even with just one user connected. (Our application accesses > SQL > > > via ADO). > > > > > > We went in and changed all the clients to use TCP/IP in cliconfg and the > > > problem seemed to be fixed. However, no-one seems to have a clue as to > > why, > > > including me - can anyone understand this, or even suggest a possible > > > reason? > > > > > > Thanks, > > > Robert Steadman > > > Vebra > > > > > > > > > > > >
All SQL logins.
[quoted text, click to view] "Kevin" <ReplyTo@Newsgroups.only> wrote in message news:%230Kh9oxnDHA.1740@TK2MSFTNGP12.phx.gbl... > trusted or sql standard login? > > > -- > Kevin Connell, MCDBA > -------------------------------------------------- > The views expressed here are my own > and not of my employer. > ---------------------------------------------------- > "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message > news:OpjBmStnDHA.2732@TK2MSFTNGP11.phx.gbl... > > We have a customer setup where all users were connecting via Named Pipes > to > > a SQL 7 server (running on NT4). This was causing a periodic "freezing" in > > our application whereby all connections to SQL were made to wait around 30 > > seconds - even with just one user connected. (Our application accesses SQL > > via ADO). > > > > We went in and changed all the clients to use TCP/IP in cliconfg and the > > problem seemed to be fixed. However, no-one seems to have a clue as to > why, > > including me - can anyone understand this, or even suggest a possible > > reason? > > > > Thanks, > > Robert Steadman > > Vebra > > > > > >
It's both. However, what we have noticed is that at the end of the "freeze"
the connections increase by 1 - not due to a new user logging on, but due to an additional process being spawned for an already connected user (which is common and never usually a problem - it's transparent to us). [quoted text, click to view] "Kevin" <ReplyTo@Newsgroups.only> wrote in message news:u$bnaK8nDHA.2536@tk2msftngp13.phx.gbl... > The reason I ask is because if you are using named pipes with sql logins, > you may be still be doing NT authentication. I've seen situations where > authentication became delayed. When you say "freezing" do you mean new > connections could not be made, or existing connections could not do work, or > both? > > > -- > Kevin Connell, MCDBA > -------------------------------------------------- > The views expressed here are my own > and not of my employer. > ---------------------------------------------------- > "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message > news:##k7hK5nDHA.1004@TK2MSFTNGP09.phx.gbl... > > All SQL logins. > > > > "Kevin" <ReplyTo@Newsgroups.only> wrote in message > > news:%230Kh9oxnDHA.1740@TK2MSFTNGP12.phx.gbl... > > > trusted or sql standard login? > > > > > > > > > -- > > > Kevin Connell, MCDBA > > > -------------------------------------------------- > > > The views expressed here are my own > > > and not of my employer. > > > ---------------------------------------------------- > > > "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message > > > news:OpjBmStnDHA.2732@TK2MSFTNGP11.phx.gbl... > > > > We have a customer setup where all users were connecting via Named > Pipes > > > to > > > > a SQL 7 server (running on NT4). This was causing a periodic > "freezing" > > in > > > > our application whereby all connections to SQL were made to wait > around > > 30 > > > > seconds - even with just one user connected. (Our application accesses > > SQL > > > > via ADO). > > > > > > > > We went in and changed all the clients to use TCP/IP in cliconfg and > the > > > > problem seemed to be fixed. However, no-one seems to have a clue as to > > > why, > > > > including me - can anyone understand this, or even suggest a possible > > > > reason? > > > > > > > > Thanks, > > > > Robert Steadman > > > > Vebra > > > > > > > > > > > > > > > > > > > >
well, if existing connections are frozen as well that rules out much to do
with a delay in authentication. I hate to stoop to this, but are you running the latest SP's on the OS and SQL? Also, I would check for indicators of performance problems using perfmon - high paging, disk queue lengths, CPU queue lengths, etc. -- Kevin Connell, MCDBA -------------------------------------------------- The views expressed here are my own and not of my employer. ---------------------------------------------------- [quoted text, click to view] "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message news:uB19l1goDHA.1740@TK2MSFTNGP12.phx.gbl... > It's both. However, what we have noticed is that at the end of the "freeze" > the connections increase by 1 - not due to a new user logging on, but due to > an additional process being spawned for an already connected user (which is > common and never usually a problem - it's transparent to us). > > "Kevin" <ReplyTo@Newsgroups.only> wrote in message > news:u$bnaK8nDHA.2536@tk2msftngp13.phx.gbl... > > The reason I ask is because if you are using named pipes with sql logins, > > you may be still be doing NT authentication. I've seen situations where > > authentication became delayed. When you say "freezing" do you mean new > > connections could not be made, or existing connections could not do work, > or > > both? > > > > > > -- > > Kevin Connell, MCDBA > > -------------------------------------------------- > > The views expressed here are my own > > and not of my employer. > > ---------------------------------------------------- > > "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message > > news:##k7hK5nDHA.1004@TK2MSFTNGP09.phx.gbl... > > > All SQL logins. > > > > > > "Kevin" <ReplyTo@Newsgroups.only> wrote in message > > > news:%230Kh9oxnDHA.1740@TK2MSFTNGP12.phx.gbl... > > > > trusted or sql standard login? > > > > > > > > > > > > -- > > > > Kevin Connell, MCDBA > > > > -------------------------------------------------- > > > > The views expressed here are my own > > > > and not of my employer. > > > > ---------------------------------------------------- > > > > "Robert Steadman" <robert.steadman@NOSPMvebra.com> wrote in message > > > > news:OpjBmStnDHA.2732@TK2MSFTNGP11.phx.gbl... > > > > > We have a customer setup where all users were connecting via Named > > Pipes > > > > to > > > > > a SQL 7 server (running on NT4). This was causing a periodic > > "freezing" > > > in > > > > > our application whereby all connections to SQL were made to wait > > around > > > 30 > > > > > seconds - even with just one user connected. (Our application > accesses > > > SQL > > > > > via ADO). > > > > > > > > > > We went in and changed all the clients to use TCP/IP in cliconfg and > > the > > > > > problem seemed to be fixed. However, no-one seems to have a clue as > to > > > > why, > > > > > including me - can anyone understand this, or even suggest a > possible > > > > > reason? > > > > > > > > > > Thanks, > > > > > Robert Steadman > > > > > Vebra > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |