Re: Large Number Of Inserts
Lee wrote:
>I have a VB6 ADO app that is inserting a large number of small records into
> SQL server 2000. Around 3900 inserts an insert fails saying that the
> connection to the server failed. It does no matter if I do this within a
> transaction or not. I get the same result.
>
> Any one know how to avoid this?
If you get a timeout error, you can set the ConnectionTimeout and/or
CommandTimeout properties of the Connection object or the CommandTimeout
property of the Command object. I believe the default is 30 seconds.
Otherwise, do you get an error message?
--
Richard
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
.
Relevant Pages
- Re: SQL Timeout Error
... I am using Express versions of SQL Server 2005 and SQL Server ... "Robert Lakinski" wrote: ... and how do I set the CommandTimeout property? ... Whether SqlConnection object establishes connection to the sql server ... (microsoft.public.sqlserver.server) - Re: Job LastRunOutCome??
... Create a connection object to the MSDB database and tie out your data ... command object to use this connection. ... I'm assuming the MSDB database would be required in a VB6 call also. ... > 'Initialise the SQL Server ... (microsoft.public.dotnet.languages.vb) - Re: Two connections with Delphi 7 Professional?
... The timeout value is also a property of TADOConnection (CommandTimeout). ... > more than one connection at a time,without any restrictions? ... Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL Server. ... (borland.public.delphi.database.ado) - Re: Blocking Access from linking SQL Server tables...
... If you have given the users permissions, ... can't deny permissions based on DNS, connection object, etc. ... > I have an Access front end that uses SQL Server linked tables. ... (microsoft.public.access.security) - Trapping ADO Connection Errors
... I have a VB6 application that uses ADO to communicate with SQL Server 2000. ... I create ADO Connection object and successfully log into SQL Server. ... (microsoft.public.vb.general.discussion) |
|