5 responses

  1. Kendra Little
    April 25, 2011

    What a great story! This is so true about how some really troubling issues can take a long time to resolve because the symptom can point to so many different things. It’s really a great team that can go through that and work together the whole time– that’s a success to celebrate.

  2. Erin Stellato
    April 25, 2011

    You make a good point, I don’t talk about how long it takes to solve the problem, but it really did take a while. And everyone persevered until they solved the problem. Excellent point, worth another post at some point :)
    Thanks for the comment, and congrats again on the new gig!!


  3. Javier Roldán
    October 30, 2011

    We have the same issue. We’are going to try to change the SCSI from Paravirtual to LSI, althought we are really worried about performance. Great post and really well explained.

    • Erin Stellato
      October 30, 2011

      I am glad you found the post useful. I hope the change helps the issue and doesn’t affect performance (it did not in this customer’s case). Let me know!

  4. Diby
    September 4, 2012

    Hi, we having the same error on a tiny 30MB database. However ours is not a virtual environment but physical with fail-over clustering for SQL Server 2008 R2. The instance herewith also host a couple of other databases, with the error only encountered on just this database.
    Our temporary way around is taking the database offline then back online, and all is well there after but i am looking for a permanent fix.

Leave a Reply




Notify me of followup comments via e-mail. You can also subscribe without commenting.

Back to top
mobile desktop