I'm not directly involved in a log shipping problem that our company is having, but I know they are having lots of problems. We use, heavily, Access 97 and ODBC to communicate with our SQL Server, with often 20 or 30 open sessions and lots of activity. Is there any chance that this would interfere with the ability to do log shipping? The users are getting ODBC time-out errors and everything slows down... before too long, we can't even TermServ to the SQL Server and we have to cold boot. -- Robert
In Access from query design view, right click in the tables ---> Properties. Look for ODBC timeout (generally the value is 60) and set it to zero. Depending on version, you can set this in Tools>Options>Advanced. I don't think Log shipping has any effect of timeouts, rather referring to SQL Server error log and SQLAgent log will give you more information. Satya SKJ Moderator http://www.SQL-Server-Performance.Com/forum This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
