Hi Debbie, You don't need to start over with a new database.
When gathering data from IM, the bug caused the importer to create duplicate entries for certain datapoints. But there's a safety mechanism where, when it tries to actually insert those entries into the database, it discovers the problem and discards the duplicates. Even so, this resulted in a significant decrease in performance, due to having to re-run the import, as well as a bunch of warnings in the log. 5.4.4 just prevents those duplicates from being created. Regarding the time it's taking to import old data, how many datasets are you exporting, and what retention policy do you have assigned to them? For comparison, we have a machine here - a couple of years old - that we use for performance testing. It has 1500 devices at a 30-second poll, 60000 interfaces and 8500 exported datasets. Starting with a fresh database, it processes roughly 3-4 weeks of historical data per day. That machine does have the advantage of not doing much besides IM & IMDC, so real-world performance will be less. But unless something else on the machine is hitting the disk, that's roughly what we expect for that number of datasets. If your experience is way off that, please let me know. Thanks, David Debbie Fligor wrote: > In reading the release notes to finally get upgraded from 5.3 to 5.4, I > noticed that 5.4.4 fixes a problem where import thinks that there are > duplicate data entries when DaylightSavings time shifts. Do I need to delete > my data-base and start the import again? ----------- David Schnur Dartware, LLC -------------------- m2f -------------------- Read this topic online here: http://forums.dartware.com/viewtopic.php?p=3551#3551 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
