Since installing SQL Server 2019 CU9, I have been getting lots of errors about NO DEK Update for almost every file.
Here is an excerpt from the SQL Server log file.
182 2/20/2021 2:07:46 PM spid25s Refresh DEK for DBID: [5] File Id: [1] – Copying encryption state
183 2/20/2021 2:07:46 PM spid25s DBID: [5] File Header for File Id: [1] was read with state = 0.
184 2/20/2021 2:07:46 PM spid25s DBID: [5] No DEK update for File Id: [1] while existing DEK is null.
185 2/20/2021 2:07:46 PM spid28s Refresh DEK for DBID: [8] File Id: [1] – Copying encryption state
186 2/20/2021 2:07:46 PM spid28s DBID: [8] File Header for File Id: [1] was read with state = 0.
187 2/20/2021 2:07:46 PM spid28s DBID: [8] No DEK update for File Id: [1] while existing DEK is null.
188 2/20/2021 2:07:46 PM spid32s Refresh DEK for DBID: [12] File Id: [1] – Copying encryption state
189 2/20/2021 2:07:46 PM spid32s DBID: [12] File Header for File Id: [1] was read with state = 0.
190 2/20/2021 2:07:46 PM spid32s DBID: [12] No DEK update for File Id: [1] while existing DEK is null.
191 2/20/2021 2:07:46 PM spid29s Refresh DEK for DBID: [9] File Id: [1] – Copying encryption state
192 2/20/2021 2:07:46 PM spid29s DBID: [9] File Header for File Id: [1] was read with state = 0.
193 2/20/2021 2:07:46 PM spid29s DBID: [9] No DEK update for File Id: [1] while existing DEK is null.
194 2/20/2021 2:07:46 PM spid26s Refresh DEK for DBID: [6] File Id: [1] – Copying encryption state
195 2/20/2021 2:07:46 PM spid26s DBID: [6] File Header for File Id: [1] was read with state = 0.
196 2/20/2021 2:07:46 PM spid26s DBID: [6] No DEK update for File Id: [1] while existing DEK is null.
197 2/20/2021 2:07:46 PM spid36s Refresh DEK for DBID: [16] File Id: [1] – Copying encryption state
198 2/20/2021 2:07:46 PM spid36s DBID: [16] File Header for File Id: [1] was read with state = 0.
199 2/20/2021 2:07:46 PM spid36s DBID: [16] No DEK update for File Id: [1] while existing DEK is null.
200 2/20/2021 2:07:46 PM spid37s Refresh DEK for DBID: [17] File Id: [1] – Copying encryption state
201 2/20/2021 2:07:46 PM spid37s DBID: [17] File Header for File Id: [1] was read with state = 0.
202 2/20/2021 2:07:46 PM spid37s DBID: [17] No DEK update for File Id: [1] while existing DEK is null.
203 2/20/2021 2:07:46 PM spid35s Refresh DEK for DBID: [15] File Id: [1] – Copying encryption state
204 2/20/2021 2:07:46 PM spid35s DBID: [15] File Header for File Id: [1] was read with state = 0.
205 2/20/2021 2:07:46 PM spid35s DBID: [15] No DEK update for File Id: [1] while existing DEK is null.
206 2/20/2021 2:07:46 PM spid38s Refresh DEK for DBID: [18] File Id: [1] – Copying encryption state
207 2/20/2021 2:07:46 PM spid38s DBID: [18] File Header for File Id: [1] was read with state = 0.
208 2/20/2021 2:07:46 PM spid38s DBID: [18] No DEK update for File Id: [1] while existing DEK is null.
It appears to happen at startup (since checkdb is run on startup) and whenever CheckDB is run.
Not sure what the cause is yet. Still investigating.
If you have seen this, please post a message about what you know on this one.
More from Stedman Solutions:
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!
I posted an un-official blog on this, it’s all ignorable.
https://www.seangallardy.com/refresh-dek-for-dbid-and-fileid-errorlog-messages/
Thanks Sean. Yes, it does appear that these are benign, and that whenever you run CheckDB on SQL Server 2019, you now get No DEK update message for each data file.
-Steve Stedman
I saw this blog post from a MS guy, he says it’s benign.
https://www.seangallardy.com/refresh-dek-for-dbid-and-fileid-errorlog-messages/
Good to hear. Thanks Brian.
Same situation here. Seems to have been snuck into 2019 CU9. For me, it’s kind of random but does happen when DBCC CHECKDB runs.
Confirmed, yes every time checkDB runs. It appears that it is benign. Still investigating. Thanks for the input.
-Steve Stedman
SQL 2019 has too many bugs, two of them I caught and send to Microsoft I have never had such bad experience with SQL during my 15 years period of working with SQL server.
Why they are not testing product in details? I think the best version is 2017 and I regret to made decision to upgrade from SQL 2017 to SQL2019.
Thanks for the information. What were the bugs you submitted to Microsoft? I would like to know so I don’t run into them.
-Steve Stedman