mhamlett
asked on
MS Sql 2000 table is set to grow unlimited but table failed to accept new INSERTs
using asp page and vbscript i was attempting to INSERT vis sql statement records to a table.
the database was set to grow unlimited and there was over 300 gig of space ont the drive where the mdf files resided. however, i was getting a script timeout when trying to insert a record. the table had about 89000 records in it. after purging the table down to 16000 records, the asp page completed properly and added records.
what reason would cause a table to stop accepting new records?
the database was set to grow unlimited and there was over 300 gig of space ont the drive where the mdf files resided. however, i was getting a script timeout when trying to insert a record. the table had about 89000 records in it. after purging the table down to 16000 records, the asp page completed properly and added records.
what reason would cause a table to stop accepting new records?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i agree with all of the above, with the exception that it should not matter how many records the table currently has. this should have no effect on the isert query whatsoever,,,since the only work being done is the insert.
I would take a look at the timeout settings you have for your connection string, and then take a look at the insert query itself....are you doing alot of pre-processing, are there 89000 fields, etc...
I would take a look at the timeout settings you have for your connection string, and then take a look at the insert query itself....are you doing alot of pre-processing, are there 89000 fields, etc...
Once records were deleted, space was freed in data and index pages, so the number of records *can* have an impact.
The only real test is to run the same INSERT from Query Analyzer, which has no timeout value. Remove ASP from the equation to eliminat the table as the source
The only real test is to run the same INSERT from Query Analyzer, which has no timeout value. Remove ASP from the equation to eliminat the table as the source
I have sometimes seen code that would pull out all records in a recordset, then add a new record to the recordset and save the recordset. Of course that will take a long time with many records.