• Brandie Tarvin (4/17/2015)


    My workplace is getting ready to upgrade to SQL 2012. While I wait for the servers to be built, I started playing with 2012 SSMS pointing to our SQL 2008 databases. It seems to me that both Intellisense and the Object Explorer Details window are incredibly slow to load and react to the mouse.

    Has anyone else noticed this behavior? I'm on a Windows 7 machine (don't know if that makes a difference).

    Yes. Just one of many problems with 2012 SSMS. I've had it "freeze" for minutes at a time. It's the worst rendition of the product I've seen yet. It also doesn't allow the scroll-wheel on many of the pulldowns and windows, requires that you setup coloring not in one place but two places (Green for Dev, Blue for Staging, Orange for UAT, Red for Prod is what I usually use), doesn't automatically update Intellisense when you add a table (you have to press {Ctrl}{Shift}{R} to do the refresh), usually doesn't register on #TempTables, etc, etc, etc. That's even on SP2 CU5, which came out mid-March.

    Rumor has it that all support and changes for 2005 are going out of scope in a year on extended support. That's good. That means that 2005 will actually be a stable product with no chance of a future change mucking up the works. 😛

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)