To do an automatic meter reading program, a total of 200 pieces of table, a half an hour to read data in a SQL database table, every upload 9600 data, including table serial number and capacity, too much worry about long database data will have a problem? Or performance degradation, I this worry is necessary? Methods this have what database configuration or optimized solutions? thank you

CodePudding user response:

After a long time, just take out the data backup and get into the historical data, not all on the table in the

CodePudding user response:

After a long time the history data in another table alone? How to automatically set the process

CodePudding user response:

Set a fixed date every month running, the operation process is the same month last year of history data backup to the history table or in the library, year interval can also be extended according to the actual business requirements,

CodePudding user response:

Make a partition, a month a partition,
In addition, as the upstairs said, also must history table,
More than 3 months of data should be put the history table,
In SQL job each month 1 time transfer data to the history table,

CodePudding user response:

reference 4 floor gypsy song response:

make a partition, a month a partition,
In addition, as the upstairs said, also must history table,
More than 3 months of data should be put the history table,
In SQL job each month 1 time transfer data to the history table,

thank you for your guidance