Reducing the size of the PowerFuse database

A brand new article has been posted to the Technote Library. This time we’re diving into the PowerTrace tables. Being new to PowerFuse, some will be inclined to switch on everything, including PowerTrace turned to the Maxx, resulting in a potentially very unwanted huge heap of logdata and perhaps even a slow performing DBMS too.

This article explains how to both cure that situation if things have gone megabad, but also how to prevent it from happening in the future. 

Click here to read the full article.

PowerTrace DBsize Estimator

This is kinda cool. This estimation tool will let you take a qualified guess at how big your PowerFuse database will be, approximatly. Now - before you jump in to it, here’s a brief reality check. The calculator only deals with the big tables in the PowerFuse datastore, namely the PowerTrace tables. These are the ones that matter when it comes to size. The rest of the database would rarely exceed 100 Meg anyway. Just to be clear, the following items are not taken into consideration:

• Custom Resources
• Uploaded .ADM files
• Desktop and Screensaver bitmaps
• Odd-sized icons
• Other stuff you upload into the database.

The PowerTrace engine in PowerFuse will create database records the moment a user starts an application or launches a website. When the user closes the app or website, the record create earlier is updated with and end-timestamp. Each record created by PowerTrace is 512 bytes in size.

The calculator is an external spreadsheet stored at EditGrid.com, where one can make online excel calculators. Have a look at the calculator by clicking on the preview image below: