SQL 2019 Standard, 32 GB, 4Core, Win 2019 vm.
We have a table with an INT Identity as PK (non-clustered)
A clustered index on a date (non-unique) about 300 rows per day. One column, that is Nvarchar(max) usually contains about 60K per record.
We need a covering index that contains the NVARCHAR(MAX) as records are accessed by a single date or small date range (2 days)
Using the clustered index on the date gives us what we need for a covering index that includes the blob column.
The indexes are maintained weekly using Ola Hallengren's script.
Outside of the NVARCHAR(MAX) the record is fairly small. The highest daily record count could eventually in years from now get up to 1000.
I know that SQL needs to maintain the uniquifyer value, forwarded records could be an issue, but I'm not sure since blob is stored separate from the data pages. My concern is decreasing performance over time. This is tied to an app and response time is important.
What are the issues if any with this sort of setup?