Hi @Ted Yin,
Thanks for your information.
This may be a bug fixed in CU release, I've checked the CU 22:
- 2330261: Fixes an assertion dump issue (Location: sebind.h:1206; Expression: bufferLen >= colLen) that you encounter when running an
INSERT
statemstatement against the table that has the nvarchar(n) column as an index column. - 2126481: Fixes an access violation dump issue that you might encounter when resuming an index rebuild that includes partitions (for example,
ALTER INDEX [index_name] ON [schema].[TableName] RESUME WITH ( MAX_DURATION = 1, MAXDOP = 1 )
).
I suggest you update the latest SQL Server 2019 CU.
Feel free to share your issue with us here.
Best regards,
Lucy Chen
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
https://docs.microsoft.com/en-us/answers/support/email-notifications