Cedar.EventStore.MsSql2008 doesn't store events in the correct order

[bwaterschoot]

Cedar.EventStore.MsSql2008 doesn't store events in the correct order

[damianh]

A solution would be in the ReadStreamForward to use StreamVersion instead of Ordinal as the orderby clause.

hmm, they should both be in the right order. It's needed when reading all streams.

[bwaterschoot]

Not sure whether you'll be able to pull that off:
http://blogs.msdn.com/b/sqltips/archive/2005/07/20/441053.aspx

[damianh]

Last resort is that I dump the TVP approach.

[yreynhout]

Isn't there a UC on the Ordinal column? Why not hand it out yourself (much like the StreamVersion)? I'm probably oversimplifying ...

[damianh]

@yreynhout it's an identity column https://github.com/damianh/Cedar.EventStore/blob/master/src/Cedar.EventStore.MsSql2008/SqlScripts/InitializeStore.sql#L13 . How would I do that from the client side? Only thing I can think of is some sort of counter that a client can 'take' x number of "ordinals"

[yreynhout]

Not from the client side, but inside the store/the script. Identity columns have been "replaced" by sequences in sql server anyway. Try it in Azure, you'll see the holes appear ...

[damianh]

SQL Server 2012 introduced support for the sequence object as an alternative to the identity column property for generating surrogate keys.

http://sqlmag.com/sql-server/sequence-and-identity-performance

Well aren't I out of date with sql server.

I want to support 2008(R2) though, does this look viable? https://blogs.msdn.microsoft.com/askjay/2012/10/08/sequence-objects-in-sql-2012-and-sql-2008/

[LeeCampbell]

I have provided a fairly simple fix in PR #20. It has been over 10 years since I wore a SQL hat, so would appreciate the criticism if it is not appropriate.