0

I'm about to design a DB for a finance institution and the last normalization of tables shows that the necessity of creating a single table for all the bank's transaction.

As per the calculations, several thousand transactions per day and this table would hit few million entires withing next few months.

1) When querying and writing data, would server perform very slow?

2) Is there any best way to handle the situation?

Improve this question
1
  • Simulate that situation with random data. A finance institution surely can permit itself a couple of benchmarks? If not a DBA.
    – Gerard H. Pille
    Commented Mar 6, 2018 at 9:26

1 Answer 1

Reset to default
1

I have seen a billion-row table hum along fine.

I have seen a thousand-row table cause the bones of the server to creak and groan.

It all depends on the queries.

"several thousand transactions per day" -- No Problem. "several thousand transactions per second" -- This gets somewhat challenging, but probably doable.

What to do?

  • Provide SHOW CREATE TABLE
  • Provide the main queries.
  • Provide the main transactions.
  • Don't do COUNT(*)
  • Don't do anything that requires hitting all 50M rows -- ask for help in reformulating such queries.

If this is really a financial institution, be sure to hire a security consultant. You do not want the hassle you will get if the data is lost/stolen.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.