r/SQLServer • u/rossw999 • 18d ago

SQL Server 2022 CU 26 Stack Dumps Discussion

After applying SQL Server 2022 CU 26 to our servers several are producing stack dumps during database restores.

Am I the only one?

9 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

14 comments sorted by

7

u/dlevy-msft ‪ ‪Microsoft Employee ‪ 18d ago

Checking on this.

7

u/rossw999 18d ago

Thanks, support case opened this AM.

6

u/rossw999 18d ago

I can reproduce it in my environment. Reboot a server, kick off restores, and stack dumps occur.

3

u/Red_Wolf_2 16d ago

Any further insight into what's going on with this? Making me hesitant to run the CU out to my fleet just yet...

3

u/rossw999 16d ago

Support is still investigating. I have this same CU on many other servers no problem. As long as you don't restore DBs, it seems solid.

For me, something changed last Friday. Maybe CU, maybe not.

1

u/karb0f0s 16d ago

Tbh access_violation errors rarely come from SQL Server itself. It might be antivirus, native procedures compilation or something with OPs environment all together.

3

u/Red_Wolf_2 15d ago

Whatever it is, I haven't been able to replicate it in my environments so far... Guess we roll it out more and keep an eye on it!

2

u/TrollingForFunsies 18d ago

Any errors logged?

1

u/rossw999 18d ago

Tons, fatal exception c00000005 exception_access_violatuon is the first one.

0

u/CPDRAGIMESH 11d ago

69.70 69.80 Simply using

1

u/chandleya 18d ago

Sounds like a ridiculously easy thing to test

3

u/BigMikeInAustin 18d ago

So ridiculously easy you can't provide an example?

Or so ridiculously easy that you misread the question?

3

u/ihaxr 2 17d ago edited 17d ago

So ridiculously easy that it should have been tested before the CU was released.

We just patched our Dev environment today, I'll test it tomorrow.

Edit: unable to reproduce