September 27, 2002 at 11:34 am
It's odd that my appl ocassionally has problem while trying to delete over 30K records in each of a few tables. Even though I didn't change the default setting for LOCK_TIMEOUT.
September 27, 2002 at 12:01 pm
I believe ODBC might have a default setting. One thing you might want to do is check the network libraries. If the application is connecting to the DB server over the network, choose TCP/IP over named pipes on the client side (you can confirm the order of your network libraries by running cliconfg.exe from the Start | Run on the client).
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
September 28, 2002 at 1:34 am
If your application is using ado to fireb the commands then set the commandtimeout property to 0.
Prakash
Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply