Search code examples
mysqldatabasedatabase-designdatabase-deadlocksdatabase-optimization

Database logic advice


I've been working on optimizing a database. The main idea with this database is that there is people populating it (several times during the day) and in parallel we have our own business people consulting it constantly and generating big reports of the data on it. I'm looking for suggestions on how should I need to structure it in order to don't make a mess on tables deadlocks because of selects or because of the amount of operations that I will be doing on it. Any thoughts?


Solution

  • Data Warehousing?

    Summary Tables speeds up "big reports", often 10-fold.

    Perhaps you also need some High speed ingestion tips? This deals with multiple writers pounding on a single 'Fact' table.