Home » Topic » Error in SQL Server 2000

Error in SQL Server 2000

Lincoln Burrows ~ Modified: September 7th, 2015 ~ ~ 1 Minute Reading

Home › Forums › Error in SQL Server 2000

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • September 8, 2015 at 11:30 am #600 Score: 0
    Andrew Jackson
    Moderator
    1 pt

    What happens if you turn off OLE DB Resource Pooling?

    'For SQLOLEDB provider
 'strConnect = "Provider=SQLOLEDB;server=MyServerName;OLE DB Services = -2;uid=AppUser;pwd=AppUser;initial catalog=northwind"

' For MSDASQL provider 
'strConnect = "DSN=SQLNWind;UID=Test;PWD=Test; OLE DB Services= -2"
    September 10, 2015 at 10:31 am #625 Score: 0
    Stephen West
    Moderator
    4 pts

    When the SQLCommand.CommandTimeout is set to zero, you expect an infinite timeout. However, versions 1.1 and 1.0 of the SqlClient provider incorrectly timeout when a response from SQL Server is broken into two packets. Immediately upon receipt of the second packet, versions 1.1 and 1.0 of the provider incorrectly timeout. The fix that is included in this article fixes this issue so that the command will have an infinite timeout.

    September 14, 2015 at 11:57 am #648 Score: 0
    Lincoln Burrows
    Moderator
    16 pts

    Thank you, maybe that will work.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.