If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘OLTP’, page 1:

DB Execution Plans for C++/Java Developers, and for anybody who has read Knuth

Quote: “If I was a compiler-with-ability-to-create-indexes-as-I-need-it – what would I do to make The Ideal Execution Plan™ for this request?”
Another Quote: “When we have that ideal-execution-plan – we still need to convince our SQL compiler to use it”
[]

OLTP DB Optimizations 101 – Thinking in Terms of Execution Plans

Quote: “to realize how our queries are working – we need to start thinking in terms of so-called “execution plans”.”
Another Quote: “it can be faster to use Table Scan rather than Index-Scan+fetch over such a low-selectivity index”
[]

Databases and RAIDs

Quote: “for quite a few applications out there, the most important feature of the RAID is not even redundancy, but greatly improved write latency. Moreover – this is the thing which we cannot possibly get from software RAID (!).”
Another Quote: “As a rule of thumb – I am trying to keep the size of OLTP DB small enough to fit into RAM of the OLTP DB Server.”
[]

Gradual OLTP DB Development – from Zero to 10 Billion Transactions per Year and Beyond

Quote: “to make an efficient representation usable for OLAP – we need to modify our data on its way to OLAP replicas”
Another Quote: “Each of the DB Server Apps is a replica master, but all replica targets are within the same Replica DB”
[]

OLTP. Compiling SQL Bindings.

Quote: “If we’re speaking about millions transactions per day over just a few hundred of different SQL statements – compiling those statements a million times (instead of a few hundred times) will be a dramatic waste of resources.”
Another Quote: “Once upon a time, I observed the largest C++ file in my career – it was a 30’000-line file(!) consisting merely of ODBC bindings (and that was just for 300 or so SQL statements)”
[]

Historical Data in Databases. Audit Tables. Event Sourcing

Quote: “99% of reporting requests and 99.9% of analytics is purely historical”
Another Quote: “Information within the audit table should be sufficient to validate/justify current state”
[]