sqlguy-736318 (5/11/2013)
How is region handling awful in SSMS 2012?Is it quirky and inconsistent or does it have a poor overall design?
Both.
It is single level and automatic, so you can't define your own regions, it tries to guess based on parsing the query window, which also leads to poor performance when editing, and it gets it's guesses badly wrong a lot of the time.
Here is a simple example of how it gets it wrong:
Thankfully SSMS 2012 is built on VS2010, so you can write your own addins quite easily, including a region handler. I had a go myself a while back using a sample on MSDN and it worked ok (similar to VS, using #region flags with titles and previews) but in the end I don't use it because I just don't need it/like it.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);