You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we upgrade V2 to V3, we have existing database with millions of record and creating index may be time-consuming.
To anticipate it, Indexes IX_Streams_IdOriginal and IX_Streams_IdOriginalReversed (and other indexes as well) better to specify WITH (ONLINE=ON)
Warning! The maximum key length for a nonclustered index is 1700 bytes. The index 'IX_Streams_IdOriginal' has maximum length of 2004 bytes. For some combination of large values, the insert/update operation will fail.
Does it mean, that MS SQL in reality support not more than 848 characters, not 1000 as declared in schema?
(it's not a problem for my IdOriginal values)
If we upgrade V2 to V3, we have existing database with millions of record and creating index may be time-consuming.
To anticipate it, Indexes IX_Streams_IdOriginal and IX_Streams_IdOriginalReversed (and other indexes as well) better to specify WITH (ONLINE=ON)
SQLStreamStore/src/SqlStreamStore.MsSql/ScriptsV3/CreateSchema.sql
Line 37 in 80189cd
Unfortunately it is required to add conditional logic as not all sql server editions support WITH (ONLINE) https://stackoverflow.com/questions/50407490/how-to-create-nonclustered-index-with-online-if-available
Btw, even WITH (ONLINE=ON) may cause blocks on the final stage
https://dba.stackexchange.com/questions/41181/why-does-create-index-with-online-on-block-access-to-the-table-over-a-period/50139#50139
The text was updated successfully, but these errors were encountered: