Nevermind. I think I found it. Someone hid a database trigger in our DB.
Why it doesn't cause the same issue on other non-prod SQL 2008 environments, I have no idea.
Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.