Langston Montgomery (11/26/2012)
Update:We upgraded the production server to SP1, and the issue is gone. Lunch for anyone who can figure out why it was happening 🙂
Seems pretty obvious what was happening: you experienced the effects of a bug in the product that was fixed by the SQL Server patch you applied. End of story. Do I get a prize?? :hehe:
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service