J
James Autry
I managed to get a performance boost from doing a batched INSERT SQL
Statement using ExecuteNonQuery rather than using the DataAdapter/Dataset
method for inserting multiple rows. I noted, however, that only so many
inserts could be batched before performance dropped again. Is this due to
server command queue cache size, or something like that?
Also, does anyone know when ADO 2.0 is supposed to come out?
Statement using ExecuteNonQuery rather than using the DataAdapter/Dataset
method for inserting multiple rows. I noted, however, that only so many
inserts could be batched before performance dropped again. Is this due to
server command queue cache size, or something like that?
Also, does anyone know when ADO 2.0 is supposed to come out?