Issue
Archiving and database size with FIFO not working
Product Line
TAC INET
Environment
I/NET site
Cause
dbo.Events keeps growing and presumably is not in FIFO mode (First In First Out)
Resolution
Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum
The size of the InetDB can be set through Microsoft SQL Server Management Tool:
- By selecting the InetDB database properties you can set the Autogrowth setting via the Files page. Under the Autogrowth column select the browse button as shown:
- The Change Autogrowth setting by either disabling the Autogrowth check box or you can set Autogrowth to a Maximum File Size as shown:
- The Autogrowth value now shows this setting is restricted to setting define in step 2.
Disabling Autogrowth allows the events to be removed from the table when the total size of the SQL database reaches the limitation set in the properties of the db.
The table dbo.Events has all the current events and it should be the biggest. The dbo.currenteventdetail table keeps up with the current max events and the current minimum events. Lets say it is around a million (1,000,000) events and so the first event in this table would be 01 and the last would be the 1000000. If items are removed from the other table, the dbo.Events, then this other table, the dbo.currenteventdetails is off. This means we run the risk of losing those events that are not correctly numbered.
Manually removing items from one table can have an impact on other tables and how this data is kept and archived.
About archiving and shrinking the db, this is a function of SQL. SQL goes into a FIFO mode, which means First In, First Out. This keeps the db from getting to large. The archived records are designated as archived in the db and even though they are still (secretly) in the db, they will be out as soon as the db is over the capacity amount and the amount designated in the db.currenteventdetail table is the guide for what is current.
The thing that keeps the db from getting to large is the archive is setup correctly and old data is archived. It is still available via Reports, but considered not technically in the db. That is what shrinks the db and keeps it from getting over size.
Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum
