|
Just started getting the following error; can anyone please advise System Error Detected: Database error #### SQLExecDirect failed with [[ODBC Error: state=22003, nativeErr=8115, err=[Microsoft][SQL Native Client][SQL Server]Arithmetic overflow error converting IDENTITY to data type int.] [ODBC Error: state=01000, nativeErr=3606, err=[Microsoft][SQL Native Client][SQL Server]Arithmetic overflow occurred.] ] for SQL=[SET NOCOUNT ON; BEGIN TRAN; INSERT INTO StatData (StatID, Value, Date) VALUES (19897, 19.51836, {ts N'2014-07-15 14:54:37'}); INSERT INTO StatData (StatID, Value, Date) VALUES (19870, 3.214874, {ts N'2014-07-15 14:54:37'}); INSERT INTO StatData (StatID, Value, Date) VALUES (19852, 1.33248, {ts N'2014-07-15 14:54:37'}); INSERT INTO StatData (StatID, Value, Date) VALUES (19899, 15.163592, {ts N'2014-07-15 14:54:40'}); INSERT INTO StatData (StatID, Value, Date) VALUES (19869, 0.022553, {ts N'[Trimmed]] |
|
I'm not a database expert but what I understand when a command has failed everything is rolled back. Because in this case the table can't have some of the values at one size and others at a different size. The process will need to start from the beginning again, sorry about that! One thought, you may want to run the database cleanup to remove older data that you may not need before running the command again. In the PASM console go to Setting -> Database Settings -> Database Cleanup. You can change the amount of days to keep the information. This process runs once a day but you could kick it off by restarting your service. It may still take a while to remove the older data as this is not a high priority process. You will be able to regain space back from the database log file after your changes if you a backup. Thanks Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer. |
|
the SQL command failed due to lack of disk space on the T-log drive, can I re-run this command and it will pick up where it failed? |
|
Hi Yes, the database will grow as the column "rowid" is increasing in size. The change in size is needed because the size of the IDs being generated are larger than the field "rowid" can handle. It has grown past what an int can hold and the field needs to be increased to the size of a bigint to handle the size of an id. Thanks Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer. |
|
Hi Quinn The SQL Command is still running after 2 hours My original SQL DB was 60gig and is now currently 80gig and growing. The SQL log file has grown from 10gig to 47gig and also is still growing... |