Hi, all

Has anyone ever see their system get dramatically slower as a table approached the 2GB file-size limitation?

We have one client with a table which is 1,975,000 KB in size. They realize that they'll need to archive some data off in the near future.

Our problem is that their entire system has slowed a great deal.

In addition there are lots of errors with no explanations. The errors listed below have been logged, yet we have verified that the code involved would not have generated them. Of particular interest are the END TRANSACTION... errors and the Not a Table errors. The END TRANSACTION line is a few lines after the BEGIN TRANSACTION line in our code, so couldn't fire without being in a transaction. The Not a Table error occurs from time to time, but when we check the table which has generated an error it's always fine. We have a routine which opens each table, adds a record, and deletes it. It is able to open every table in the system.

They have been getting the following errors for the past week (I have shown the number of times each error has occurred in addition to the error message):

Count  Error
38     Record is in use by another user.
17     END TRANSACTION command cannot be issued without a corresponding BEGIN TRANSACTION command.
08     Not a table.
04     Database object is being used by someone else. 
03     Table has no index order set.
02     Uniqueness of index APPLDID is violated.
01     Error reading file.

Also, they are getting Fatal Errors at the rate of 2-3/hour.

We checked all the tables' indexes, and re-created them all, so we don't think index corruption is to blame.

Anyone else ever see all these (seemingly) incorrect errors?

Thanks.

- George [scratching my head in puzzlement]