V0N_hydro
Member
the factory talk SE (distributed) historical alarms activex widget was taking longer and longer to actually load any old alarms in to the table, and finally quit working at all.
There is a 10GB limit on the SQL Express database file size which we had run in to in only 8 months. It turns out that there were 16 alarms that were being disabled and enabled rapidly because they were programmed to be disabled when the analog input fault status was raised, and enabled when it was cleared. there was nothing wired to the analog inputs, they were provision for a 'future sensor', and should have had fault status the entire time.
I deleted 25 million rows from the database which took 4 hours and deleted the unused alarms from the programs so they won't cycle their enabled status anymore.
Does anybody have a method for automatically purging events older than X from the historical alarm database, or when the number of events is > Y?
My techconnect contract has expired, and the other references to the factory talk historical alarm database i've found on this forum don't have any resolutions other than Allen Bradley support telling their customer to break out the VBA and program it themselves.
There is a 10GB limit on the SQL Express database file size which we had run in to in only 8 months. It turns out that there were 16 alarms that were being disabled and enabled rapidly because they were programmed to be disabled when the analog input fault status was raised, and enabled when it was cleared. there was nothing wired to the analog inputs, they were provision for a 'future sensor', and should have had fault status the entire time.
I deleted 25 million rows from the database which took 4 hours and deleted the unused alarms from the programs so they won't cycle their enabled status anymore.
Does anybody have a method for automatically purging events older than X from the historical alarm database, or when the number of events is > Y?
My techconnect contract has expired, and the other references to the factory talk historical alarm database i've found on this forum don't have any resolutions other than Allen Bradley support telling their customer to break out the VBA and program it themselves.