Depending on the model and software version of the Security Management System (SMS), different amounts of data can be stored by the SMS. You can increase or decrease the amount of data by editing the settings under Admin→Database, selecting the appropriate database and clicking on the Edit button to make any changes.
If you are unable to increase the number of "Max Rows" for the database, it is most likely caused by the fact that the current database was restored from a previously older version of the SMS and that version of the SMS had a lower maximum number. When you perform an SMS restore from a previous SMS version the database structure from the restore file is used.
Example: Let’s say you just received an SMS H3 XL from TippingPoint. This new server is deployed from the factory with SMS v4.4.0 and it can store a maximum of 500 million historical events.
Your old server is an SMS 2000 XL with SMS v3.6.0, managing 200 devices and it can store a maximum of 100 million historical events. You wish to transfer the current configuration to the new sever and in order to do so you create a backup of the old server to restore onto the new server. Once you deploy the new server you perform a database restore from the old server to the new.
Since you performed an SMS restore from your old SMS server (v3.6.0) to your new SMS server (v4.4.0), the system will use the database structure of the old SMS (v3.6.0) which calls for 100 million historical events not 500 million as allowed by SMS v4.4.0.
The only way to maintain the 500 million max rows from SMS v4.4.0 is to not perform a restore from an older version of the SMS but instead perform a brand new installation which would include importing all the devices onto the new SMS.