November 25, 2021 at 4:17 am
Hi Jeff
Apologies for delaying in replying. Ive been ill with a bad cold .
This is what I see of the the table when i run sp_help 'dbo.SIData_222222_88_20211103_1436'
At least it's "only" a cold. 😀 Hope you feel better soon and can wolf down a good piece of pumpkin pie and a glass of milk tomorrow. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
November 25, 2021 at 4:28 am
Man, I thought we might have had it with the RCSI thing. You've answered all the other questions with the graphics. I see absolutely nothing in any of that that could be causing this issue.
The only thing I could ask now is for you to run the following code and then do the same checks that you did before just to see if it's affected the same way. If it is, you may have uncovered some whacko bug in SQL Server 2019.
-- DROP TABLE IF EXISTS dbo.JustaTest;
CREATE TABLE dbo.JustaTest
(
ReadingDateTime DATETIME2(2) NULL
,ReadingValue REAL NULL
) ON [PRIMARY]
;
GO
INSERT INTO dbo.JustaTest
(ReadingDateTime,ReadingValue)
SELECT TOP 10000000
GETDATE(),1.0
FROM sys.all_columns ac1
CROSS JOIN sys.all_columns ac2
;
GO
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2021 at 10:17 am
Hi Jeff
Apoolgies for delaying in replying. Im back at work after feeling poorly
Now i ran the code you supplied to create the test table. Attached are the screen shots from the checks i ran
after creating the table
November 29, 2021 at 12:41 pm
do you mind running this again and ensuring that the dbname is correct
select snapshot_isolation_state
, snapshot_isolation_state_desc
, is_read_committed_snapshot_on
, is_memory_optimized_elevate_to_snapshot_on
from sys.databases
WHERE database_id = DB_ID('yourdbname')
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply