By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,269 Members | 1,332 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,269 IT Pros & Developers. It's quick & easy.

SLOW oh so slow

P: n/a
con
Hi All,

I have a asp.net web site with vb.net back end, when I connect to the MS sql
2000 server via ado.net it takes a long time to connect to ms sql >25sec.

Addressed sql server via ip, full network name & computer name.

I have enabled pooling, watched the traffic via netmonitor and it has a
number of tds protocol item.

Security is via ad groups, and I have also tried direct user ids.

iis 6.0, Framework 2.0, vs 2003 sql server on seperate server if you need
further information please ask.

Thanks in advance.

Jun 27 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
The only reasons I can imagine why it would take that long to connect to SQL
server is due to the distance between your website and the server, or the
data server's processor is at 100% usage. If your web app is in New York,
and your data server is in India it's going to take a while. I work on the
east coast and our data server is on the west coast - so I totally
understand your frustration.

The closer your app and data servers are to each other the quicker your
response time will be. If your servers are in the same building and still
doing that, well, I have no idea what could cause that. Also, if you can't
get the data and app servers closer to each other and you haven't already
done this - start caching common data that doesn't change frequently in
memory within your app. That will help fix the issue since the application
won't have to query the server as often.

"con" <Co*@nospam.nospamwrote in message
news:eC**************@TK2MSFTNGP02.phx.gbl...
Hi All,

I have a asp.net web site with vb.net back end, when I connect to the MS
sql 2000 server via ado.net it takes a long time to connect to ms sql
>25sec.

Addressed sql server via ip, full network name & computer name.

I have enabled pooling, watched the traffic via netmonitor and it has a
number of tds protocol item.

Security is via ad groups, and I have also tried direct user ids.

iis 6.0, Framework 2.0, vs 2003 sql server on seperate server if you need
further information please ask.

Thanks in advance.
Jun 27 '08 #2

P: n/a
con


I agree, but in this case both servers are in the same data center which is
why I am so confused.

"Jeff Winn" <jw***@nospam.comwrote in message
news:A0**********************************@microsof t.com...
The only reasons I can imagine why it would take that long to connect to
SQL server is due to the distance between your website and the server, or
the data server's processor is at 100% usage. If your web app is in New
York, and your data server is in India it's going to take a while. I work
on the east coast and our data server is on the west coast - so I totally
understand your frustration.

The closer your app and data servers are to each other the quicker your
response time will be. If your servers are in the same building and still
doing that, well, I have no idea what could cause that. Also, if you can't
get the data and app servers closer to each other and you haven't already
done this - start caching common data that doesn't change frequently in
memory within your app. That will help fix the issue since the application
won't have to query the server as often.

"con" <Co*@nospam.nospamwrote in message
news:eC**************@TK2MSFTNGP02.phx.gbl...
>Hi All,

I have a asp.net web site with vb.net back end, when I connect to the MS
sql 2000 server via ado.net it takes a long time to connect to ms sql
> >25sec.

Addressed sql server via ip, full network name & computer name.

I have enabled pooling, watched the traffic via netmonitor and it has a
number of tds protocol item.

Security is via ad groups, and I have also tried direct user ids.

iis 6.0, Framework 2.0, vs 2003 sql server on seperate server if you need
further information please ask.

Thanks in advance.
Jun 27 '08 #3

P: n/a
Have you tried connecting to the server from a source other than your site?
If you have the same issue connecting to the server with sql management
studio it might help narrow down the problem.

"con" <Co*@nospam.nospamwrote in message
news:uC**************@TK2MSFTNGP02.phx.gbl...
>

I agree, but in this case both servers are in the same data center which
is why I am so confused.

"Jeff Winn" <jw***@nospam.comwrote in message
news:A0**********************************@microsof t.com...
>The only reasons I can imagine why it would take that long to connect to
SQL server is due to the distance between your website and the server, or
the data server's processor is at 100% usage. If your web app is in New
York, and your data server is in India it's going to take a while. I work
on the east coast and our data server is on the west coast - so I totally
understand your frustration.

The closer your app and data servers are to each other the quicker your
response time will be. If your servers are in the same building and still
doing that, well, I have no idea what could cause that. Also, if you
can't get the data and app servers closer to each other and you haven't
already done this - start caching common data that doesn't change
frequently in memory within your app. That will help fix the issue since
the application won't have to query the server as often.

"con" <Co*@nospam.nospamwrote in message
news:eC**************@TK2MSFTNGP02.phx.gbl...
>>Hi All,

I have a asp.net web site with vb.net back end, when I connect to the MS
sql 2000 server via ado.net it takes a long time to connect to ms sql
>25sec.

Addressed sql server via ip, full network name & computer name.

I have enabled pooling, watched the traffic via netmonitor and it has a
number of tds protocol item.

Security is via ad groups, and I have also tried direct user ids.

iis 6.0, Framework 2.0, vs 2003 sql server on seperate server if you
need further information please ask.

Thanks in advance.
Jun 27 '08 #4

P: n/a
con

Got it working,

I had the ms ajax library removed from the servers and now all is well,
just the application runs in non aja mode but it is fast. Now all I got to
do is get it orking with AJAX.

Thanks for the help
"Jeff Winn" <jw***@nospam.comwrote in message
news:6B**********************************@microsof t.com...
Have you tried connecting to the server from a source other than your
site? If you have the same issue connecting to the server with sql
management studio it might help narrow down the problem.

"con" <Co*@nospam.nospamwrote in message
news:uC**************@TK2MSFTNGP02.phx.gbl...
>>

I agree, but in this case both servers are in the same data center which
is why I am so confused.

"Jeff Winn" <jw***@nospam.comwrote in message
news:A0**********************************@microso ft.com...
>>The only reasons I can imagine why it would take that long to connect to
SQL server is due to the distance between your website and the server,
or the data server's processor is at 100% usage. If your web app is in
New York, and your data server is in India it's going to take a while. I
work on the east coast and our data server is on the west coast - so I
totally understand your frustration.

The closer your app and data servers are to each other the quicker your
response time will be. If your servers are in the same building and
still doing that, well, I have no idea what could cause that. Also, if
you can't get the data and app servers closer to each other and you
haven't already done this - start caching common data that doesn't
change frequently in memory within your app. That will help fix the
issue since the application won't have to query the server as often.

"con" <Co*@nospam.nospamwrote in message
news:eC**************@TK2MSFTNGP02.phx.gbl...
Hi All,

I have a asp.net web site with vb.net back end, when I connect to the
MS sql 2000 server via ado.net it takes a long time to connect to ms
sql >25sec.

Addressed sql server via ip, full network name & computer name.

I have enabled pooling, watched the traffic via netmonitor and it has a
number of tds protocol item.

Security is via ad groups, and I have also tried direct user ids.

iis 6.0, Framework 2.0, vs 2003 sql server on seperate server if you
need further information please ask.

Thanks in advance.
Jun 27 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.