In this survey I’d like to know what your experience is using the DBCC WRITEPAGE undocumented command.
This survey is closed – see the editorial here – thanks!
I’ll editorialize the results in a week or two.
Thanks!
In the previous Curious Case I described an issue Jonathan had at a client with very long IAM chains, and the circumstances leading to it.
(The original version of this post first appeared on the now-deleted SentryOne blog at the start of 2022.) One of the most fundamental concepts in
(This post first appeared on SQLperformance.com four years ago as part of a blog series, before that website was mothballed later in 2022 and the
(This is from the Insider Newsletter that I sent out earlier today…) Back in early 2023 I wrote a long blog post about my struggles
This is a case that happened on a client system last year: occasionally a common query on a tiny table appeared to ‘hang’ and had
(TL;DR; Video trailer for the new course is here.) Joe’s next course, AIVSP: Vector Search in Practice, is now available! This online course builds on AIVSE:
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
5 thoughts on “Survey: using DBCC WRITEPAGE”
None.
I’ve only used it to poke around and corrupt test databases in my own private lab. I’d never use this command outside of that.
Played with some of the techniques as you demonstrated in the SQL PASS 2013 pre-con.
Used this as an MCT, it was part of the piecemeal recovery lab for the instructor to corrupt the database. Never in a live environment (Test/QA/Prod).