SQL Server Stored Procedure timeout

  • Thread starter Thread starter Ross
  • Start date Start date
R

Ross

I am passing a stored procedure from MS Access to SQL server and it is
timing out.

If I hit debug and run again, about 50% of the time the procedure will
completely execute before timing out again (a second time).

How do I extend the time out properties of access so that the stored
procedure in SQL server has time to run?

There are no ODBC connections involved with this scenario. I am just update
SQL server tables.

If I run the stored procedure directly from SQL server, it runs in about 10
to 25 secs.


Thanks

Ross
 
On Wed, 18 Mar 2009 06:20:04 -0700, Ross

If you're not using ODBC, what *are* you using?
Read up on "passthrough query"; it will likely do what you need.

-Tom.
Microsoft Access MVP
 
I am actually just using MS Access (front end) to run SQL Server (Back end).
All of the code, all of the tables, all of the queries are SQL server
procedures.

I am simply firing stored procedures from Access instead of firing them
directly for SQL server.

I am not returning data to MS Access so there is no need for ODBC connections.
 
Question, is this an MDB or an ADP?

In an MDB, you use a Pass-through query with the EXEC command to run the
stored procedure. You still need an ODBC connection string in the PT query
and you can set the ODBC Timeout property to a larger number (60 is default,
I think) so it won't time out on you. Or if you set the Timeout to 0, it
will never timeout.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
Back
Top