SQL Server Timeout

[Chris Kennedy]

I am connecting to SQL server 2000 via ASP using an ADO recordset and OLEDB
connection. Occasionally I execute queries though the execute method of the
connection. Just recently this has started giving a timeout expired error
but will allow me to delete via the recordset delete method. It's not a huge
problem to do this but many other sites use direct SQL execution and I am
worried that they will stop working. Also sometimes it will work and
sometimes it won't. Is this something obvious that people have come across
before. If anyone could give me some pointers, that would give me something
to start on before I start asking my manager to start looking at IIS or SQL
server. I'm OK on the design side of SQL server but don't have much
experience on doing diagnostic/profiling type stuff.

[Aaron Bertrand - MVP]

Some tools and KB articles here that might help.
[url]http://www.aspfaq.com/2513[/url]

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




"Chris Kennedy" <nospam@microsoft.com> wrote in message
news:e6OpE#7wDHA.1740@TK2MSFTNGP12.phx.gbl...

> I am connecting to SQL server 2000 via ASP using an ADO recordset and

OLEDB

> connection. Occasionally I execute queries though the execute method of

the

> connection. Just recently this has started giving a timeout expired error
> but will allow me to delete via the recordset delete method. It's not a

huge

> problem to do this but many other sites use direct SQL execution and I am
> worried that they will stop working. Also sometimes it will work and
> sometimes it won't. Is this something obvious that people have come across
> before. If anyone could give me some pointers, that would give me

something

> to start on before I start asking my manager to start looking at IIS or

SQL

> server. I'm OK on the design side of SQL server but don't have much
> experience on doing diagnostic/profiling type stuff.
>
>

[îÁÉÌØ óÉÂÇÁÔÕÌÌÉÎ]

Hello!
I'm using next command to avoid problem with timeout
Server.ScriptTimeout = 300
it sets timeout interval to 5 min.


"Chris Kennedy" <nospam@microsoft.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:e6OpE#7wDHA.1740@TK2MSFTNGP12.phx.gbl...

> I am connecting to SQL server 2000 via ASP using an ADO recordset and

OLEDB

> connection. Occasionally I execute queries though the execute method of

the

> connection. Just recently this has started giving a timeout expired error
> but will allow me to delete via the recordset delete method. It's not a

huge

> problem to do this but many other sites use direct SQL execution and I am
> worried that they will stop working. Also sometimes it will work and
> sometimes it won't. Is this something obvious that people have come across
> before. If anyone could give me some pointers, that would give me

something

> to start on before I start asking my manager to start looking at IIS or

SQL

> server. I'm OK on the design side of SQL server but don't have much
> experience on doing diagnostic/profiling type stuff.
>
>