• My second worst frustration in working with an ERP system written in .NET and running on SQL Server is encountering intermittent data loss or corruption.

    When you trace through the code, everything looks clean, but somehow out of clean code, and clean input, data was lost or garbage was created.

    My absolute worst frustration is that these occurences are considered "acceptable."

    Our ERP vendor once supplied a patch and noted that installing it would "make data loss less likely." (actual quote)

    So, my question to the group is: What, if any, is an acceptable error rate for data loss or corruption on SQL Server?