| [SQLDownUnder] Real time enterprise database design |
- From: Tanvir Huda
- Subject: [SQLDownUnder] Real time enterprise database design
- Date: Sun, 11 Feb 2007 22:53:06 -0800
- Follow-Ups:
- Prev by Date: RE: [SQLDownUnder] .net sql provider and automatic char to nchar conversion
- Next by Date: RE: [SQLDownUnder] Real time enterprise database design
- Previous by thread: RE: [SQLDownUnder] Sql 2000 bug
- Next by thread: RE: [SQLDownUnder] Real time enterprise database design
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
Hello Guys I know this is basic and different people do that in
different ways according to their needs; but I would like to know about the
best practices to design a highly scalable real time enterprise databases for
financial institutions. When are we making transaction how the record is kept and
tables are designed? This is must not be basic ER solutions. The database must
be designed to ensure a highly scalable,high performance and high throughput
one. So, when millions of people are making transactions for their day-to-day
saving accounts how the records are kept and how they are updated. Don’t think
about 100s, I am thinking about thousands per minutes. So, when a transaction
has been made their current balance is available at the next moment for next
transaction or view. This is done both at the application software and hardware
level. My objective is to know the best practices in software
industries in tackling this issue. Thanks for your co-operation in advance. Regards Tanvir |
(Click here for more information on the sqldownunder mailling list)
