Hi,
We recently placed a new E-Commerce site into production using ASP.NET
& ADO.NET and SQL Server 7.0. We've been having issues with database
timeouts that weren't an issue with our older, ASP site and the same
database server. We currently have the timeout set to 45 seconds in
our connection string. These procs should never run longer than 45
seconds. Most of them either pull back small amounts of customer
information or update/insert a small number of records in various
tables.
Slowness is not experienced while accessing the server through query
analyzer, reports, other apps etc.. Is there any issue with using the
..NET platform and SQL Server 7.0?
Chris
We recently placed a new E-Commerce site into production using ASP.NET
& ADO.NET and SQL Server 7.0. We've been having issues with database
timeouts that weren't an issue with our older, ASP site and the same
database server. We currently have the timeout set to 45 seconds in
our connection string. These procs should never run longer than 45
seconds. Most of them either pull back small amounts of customer
information or update/insert a small number of records in various
tables.
Slowness is not experienced while accessing the server through query
analyzer, reports, other apps etc.. Is there any issue with using the
..NET platform and SQL Server 7.0?
Chris