From the documentation, it seem that we can not purge BBSM records in the report Database. Does somebody care about the management of those records, if yes how ?Can it happen that the database get full and that BBSM crash ?
I would not worry about the radius database. I have never seen an issue with it before. If you want to see the database schemas take a look here:
As a regular maintenance item I would clear out the transaction history and debugging tables. These should not cause the BBSM to crash but can cause a performance hit.
Purge both the transaction history and debugging tables. This can be done via SQL commands. MSDE has a 2GB limit per database. The past history in the transaction history will be purged. If you want to save this data in a text file, use the following:
Bcp "use atdial select * from transaction_history" queryout -T -c
The above will export the table to a tab delimited text file. It will be very large and notepad will not be able to open this file. You will need
to use excel, access or some other text editor that can handle large files.
The next step is to purge the two tables. These will be the largest tables especially if they have been using debug. Transaction_history is
written to constantly and needs to be purged on occasions.
From the command prompt
OSQL -d atdial -E
> delete transaction_history
> delete debugging
Hope this helps.