• We get these debates where I work a lot. For some reason, many of my fellow DBA's believe that every known bug has to be addressed prior to release or you absolutely can not release the software. I fall into the pragmatic camp. Does it break stuff, or just not work as well as we would like? If it's the latter, deploy it and we will get around to fixing it, if it needs fixing. The fact of the matter is, sometimes, what appears to be "broken" to us, is just fine to the users. What appears to be very slow to us, is fast enough for the users. If it isn't, usually, not always, but usually, the word will get back to us and we can spend time fixing what needs fixing. In the mean time, something that the users need is available, rather than sitting on a Dev server waiting for perfection.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning