3,035
edits
Changes
→Breakpad Database
= Breakpad Database =
Designing the schema is an important task and shouldn't be taken lightly. In general, there are typically two routes to take:* Define Normalize, come up with a snowflake-like schema that works well with current query/reporting needs, abstract up-front but better long-term** Need to define metadata that Leave denormalized, just swallow inefficiencies in the short term and pay the price later on How we absolutely have to can haveboth:** Other information and common reports that any crash reporting system would haveNormalize properly, generating a properly abstracted set of tables with partitions** [need Use views to dig up all pull together common queries - jay]used for reporting The current schema has:
* The schema now accounts for the following kinds of information
** individual minidump records
** product/OS/buildid information
** control information used to "register" an incoming minidump and monitor/track/control its progress though all the stages from being transfered from the client until it is fully collected and processed on the server and available for reporting and analysis.
A major concern about over-normalization is data insertion and the problems it presents for the processor, which should probably be transactional and may have to do lookups and some db magic in order to successfully insert new records.
* using the same database and schema for the minidump data and also for control over the processing of the minidumps has created problems in the past. when coruption is introduced, database performance problems crop up, or maintenance is required to manage the collection of minidumps, the processing of incoming minidumps is hindered and we start into a downward spiral of compounding problems. We should do some thinking to see if there are ways to improve on the existing design.
