[dba-SQLServer] ODBC Timeouts from SQLServer?

One method is to run your queries in the Query Analyzer to see just
how long they take, another method is to turn on the Sql Profiler to
find out exactly how long they are taking, you'll need to be available
for both.  Many times IME it's been access that times out before sql
server tho...

--
Francisco

On 10/3/06, John Skolits <askolits at ot.com> wrote:
> I have a bunch of reports that run at night (within Access MDB).
> The database is triggered by using command line arguments.
> Sometimes, I get an ODBC timeout error, but it's very inconsistent.
> I set all the query ODBC timeouts to 300 seconds.
> These routines run at about 2:30 AM to avoid heavy server loads. But, I do
> know, there are other backups and such running that take processor time, but
> my MDB queries typically run very fast.
>
> Is it possible SQLServer is timing out instead of Access and that's why the
> messages are happening.
>
> There are many more ways I can optimize the queries, which is the next step,
> but how to I find out what the SqlServer ODBC timeout value is and how do I
> change it?
>
> John
>
>
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>


-- 
-Francisco
http://sqlthis.blogspot.com | Tsql and More...