title: How can I cause consistency error in SQL Server?
body: <p>I've got following error in <code>dbcc checkdb</code> output from our customer for one table (more of very similar lines):</p>
  
  <blockquote>
    <p>Msg 8964, Level 16, State 1, Line 1<br>
    Table error: Object ID 212503619, index ID 1, partition ID 72057594046251008, alloc unit ID
    72057594048675840 (type LOB data). The off-row data node at page (1:705), slot 0, text ID 328867287793664 is not referenced.</p>
    
    <p>CHECKDB found 0 allocation errors and 49 consistency errors in table 'X' (object ID 2126630619).</p>
  </blockquote>
  
  <p>This error was created when running upgrade of our software (if he restores DB from backup and run the upgrade again, the same issue reappears).</p>
  
  <p>My question is - how can I possibly create this kind of error from my app? I always thought that this kind of error must be caused by some environmental (HDD) problem, but I've seen the same issue on the same table on another environment. I tried the same steps as him, but without success. </p>
  
  <p>Thanks!</p>