3 ms·
Go with what you have experience in. If you build it and it is not fast enough, then throw caching at it. There probably won't be a huge difference between most
by watmough 19y ago
Go with what you have experience in. If you build it and it is not fast enough, then throw caching at it. There probably won't be a huge difference between most databases, if used effectively.
If you have special requirements, such as true isolation in transactions, be aware that this is "leading edge" for SQL Server 2005, and probably for MySQL. On the other hand, Oracle has been doing it for years.
If the data is being streamed in, and timestamped, and stored, you may want to just hold it in memory (32 Gigs holds a lot of data) or write to flat files. For simple data types, that are used in a predictable way, not much beats well-written custom code.