by Michael S. Kaplan, published on 2008/03/16 10:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2008/03/16/8237443.aspx
Please read disclaimer; content of Michael Kaplan's blog not approved by Microsoft!
At first blush, it reminded me of my own battles with KeysEx vs. KeySex or ControlsEx vs. ControlSex.
With shades of the whole PenIsland vs. PenisLand conundrum when it was revisited.
But when I was sitting in Mary Chipman's temporary Redmond office on a Saturday afternoon and she was looking at the What's New in SQL Server 2008 topic while I set up parts of her Latitude D830 as penance for the mistakes I made the day before in helping her set it up (accidentally using an evaluation version ISO for a VPC) we both got a huge laugh.
Why, you might ask?
Well, clicking on a link and getting to the Using the FORCESEEK Table Hint topic.
Clearly this all-caps
FORCESEEK
could be looked at either [as they intended it ]as
FORCE SEEK
or what it suggested to Mary and I as we were being required (IOW forced) to install countless programs and patches
FORCES EEK!!!
It all depends on how you look at the new keyword? :-)
This post brought to you by ! (U+0021, aka EXCLAMATION MARK)