I’m running into a problem inserting rows from a file with 13,000 rows into a SQL Server 2008 database. I can take a small chunk of the file and insert it just fine. I’ve been able to insert as many as 4000 rows in a single transaction (yes, I’m using transactions), but when I use something higher I get a server 500 error.
Is there a limit on how many rows you can Commit or Rollback in SQL Server using an SQLOLEDB database connection in classic ASP? If so, how do I increase that?
If not, what other things should I look for in both IIS and SQL Server to ensure I can insert that many rows?
I’m not aware of any limit in the #/rows for a single transaction (a “transaction” being a T-SQL “begin tran”/”commit”).
There are lots of limitations in “classic ADO” (the data access API used by “classic” ASP 3.0 and VB6). But frankly, I don’t recognize any of them as being applicable to this scenario.
Q: What does your actual ADO “insert” look like? Could you cut/paste the code here?
Q: Have you looked at your IIS server logs? At your MSSQL server logs? Are any ADO exceptions being generated (your are detecting client side errors, aren’t you?).