I have been advising my clients to go to 3186 and stop there for now. I got some validation for that last night on the SQL MVP monthly topics call where one of the guys mentioned having significant problems with builds above that number, especially in clustered environments. I just picked up a new client that went to 3200 on one of their (clustered) production machines because they were getting demonstrated issues with one of the bugs fixed by that build. Wonder how that will work out.
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service