Doris Manning
mikedorism at verizon.net
Sun May 4 08:07:01 CDT 2008
The culprit is probably a system database called "tempdb". This database gets reset each time you stop and restart SQL Server. In my world, I had to create a job to shrink it every hour in order to resolve this issue. http://sqlserver2000.databases.aspfaq.com/why-is-tempdb-full-and-how-can-i-p revent-this-from-happening.html Doris Manning Database Administrator Hargrove Inc. -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Sunday, May 04, 2008 8:02 AM To: VBA; Dba-Sqlserver Subject: [dba-VB] SQL Server timeouts I am running this process that updates SQL Server from VB.Net. The process runs normally for tens of millions of records, then SQL Server "hangs" and stops servicing requests (from this process), either reads or writes. It just times out with error messages "Timeout Expired: The timeout period expired prior to completion of the operation or SQL Server is not responding". This is not a once off occurrence, it happens every time I start the process running. Sometimes I get this and then eventually SQL Server will start responding, sometimes it just stops responding. How do I troubleshoot this? -- John W. Colby www.ColbyConsulting.com _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com