Using an RDBMS as event sourcing storage

Question

If I were using an RDBMS (e.g. SQL Server) to store event sourcing data, what might the schema look like?

I\'ve seen a few variations talked about in an abstract sens

Answer 1

Possible hint is design followed by "Slowly Changing Dimension" (type=2) should help you to cover:

• order of events occurring (via surrogate key)
• durability of each state (valid from - valid to)

Left fold function should be also okay to implement, but you need to think of future query complexity.