This is quite an unusual situation, and I wonder if you haven't stumbled upon a bug (possibly known?). I hope the TF 4134 does you right, which would mean the bug WAS fixed - it just wasn't generally released due to the query plan regressions the fix caused. That actually sounds probable. But I was DEFINITELY disappointed to see that TF4134 was NOT bundled under 4199. Perhaps because it wasn't a true "performance fix", but still..
As for me, I have had a horrifically bad year from a medical standpoint. I have lost 60-70% of potential billable hours since May when I had a surgery that went south. Quality of life is still awful, I still have to take percocet and do other things to help mitigate the pain and discomfort, and a specialist said a month ago "there's nothing we can do right now. but the pain and other effects usually resolve themselves over time". If/when that happens I may well have to go under the knife again to address the original issue that actually didn't get fixed.
Other than all that, and the significant emotional and psychological issues that go with it, things are actually pretty decent. Thankfully my long-term standing clients have stuck by me. Family support has been great too.
That which does not kill us makes us stronger, right?!?
I hope things are better in your world?!?
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service