Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />. <br /> <br />IntervalAreaAvg: eontains interval area averages for overlay caleulations <br /> <br />SysMessages: eontains any system status or error messages that haven't been deleted <br /> <br />Once the data have been transferred to archive2,mdb, use MS Aeeess to copy the data elsewhere <br />and/or further proeess the data without introducing additional overhead into the on-line proeessing of <br />data, <br /> <br />Backup of the whole database <br />The sites, sensors, geography and other funetional instructions for your STORM Wateh system are <br />also stored in the database, Thus, the whole database should be eopied elsewhere periodically, by <br />default as swback2.mdb, In the event of some problem, you will be able to both retrieve data and <br />restore your program settings, <br /> <br />Please see Warning above about baeking up the hard drive, <br /> <br />Archive options <br />These options determine the overall funetions of the Arehive utility, A standlrd setting might provide <br />automatie arehiving every day, with reeords older than 31 days being eo pied and then purged from <br />the data eollection database, <br /> <br />When DataChron records are removed through arehiving, you ean no longer see individual records in <br />the graphieal or tabular displays or in the data base view. However, time series rain summaries, <br />hourly and daily rain totals, are kept for mueh longer periods, and you ean view them on the rain bar <br />graphs, <br /> <br />Archiving and performance <br />There is a trade-off between system performanee and the amount of data you keep available on-line; <br />for a system with a fast proeessor, you may not see a significant performanee ehange until there are <br />more than one or two hundred thousand records in the DataChron table, <br /> <br />Change the settings to best serve your system, Experience will guide you in determining how many <br />reeords ean be kept ol1-line without degrading performance, <br /> <br />Run maintenance every day: If eheeked, arehiving will take plaee without user input <br /> <br />Append records to archive database: Copies reeords to arehive file, from now on baek to last <br />update <br /> <br />Purge operational records after (days): Removes appended records from operational database <br /> <br />Compact operational database: Reeovers otherwise wasted disk space - removing records <br />doesn't recover disk spaee <br /> <br />Copy database to another location every (x) days: Makes a copy of the ol1-line database file to <br />some other location, It will write over the previous eopy at that location, <br /> <br />Database locations <br /> <br />Speeify full path names for arehive am baekup databases, <br /> <br />Additional data to archive: <br /> <br />19 <br />