Post reply

Features, etc that cannot be managed from a previous version of SSMS?

  • August 24, 2015 at 7:16 am

    #302266

    I've got a request from one of the devs where are work about going to SQL2014 in our next migration (we're currently SQL2008R2 SP3 across the board.) One of the potential pitfalls I can see is managing SQL2014 plus some of the things other developers are used to doing may not work.

    So the question is, are there any SQL2014 features that could not be managed via SSMS (GUI, not scripts,) such as I've run into with managing SQL2012 from SSMS 2008R2 (SSIS, Extended Events, etc?)

    Also, would developers be able to use the "New Table" designer function in SSMS 2012 against a SQL2014 server?

    My feeling is probably not to the latter, and yes to the first.

    Before you suggest using SSMS 2014 (the obviously correct solution,) a bit of background: We deployed a couple SQL2012 servers a few months back. I'm still waiting on our IA / desktop admin guys to give approval to install SSMS on my laptop to manage said servers (I'm currently making due with SSMS 08R2, and RDP'ing into the QA SQL2012 box when I need XEs etc...)

    Thanks all,

    Jason

  • August 24, 2015 at 7:25 am

    #1821949

    There's no way around it: some features don't work correctly or are completely missing with older versions of SSMS.

    Talk with your desktop support team and let them know how important their approval is for your work. If they don't listen, escalate to their manager: if it really is important, it will get through.

    -- Gianluca Sartori

  • August 24, 2015 at 7:30 am

    #1821951

    SSMS 2012 tends to throw odd errors intermittently when connected to a SQL 2014 server. I had ignorable errors show up any time I right-clicked on anything in object explorer.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 24, 2015 at 7:43 am

    #1821955

    Thanks both, that's pretty much what I expected the answers to be.

    Gianluca, even with my boss pushing, it took almost two months and counting for SSMS 2012. Still waiting on the desktop guys to approve the "build guide" for installing it on a desktop system...

    :-/

  • August 24, 2015 at 1:03 pm

    #1822080

    I install all versions of SSMS and BI studio that are in my environment starting with the oldest. SSIS packages, SSRS reports, maintenance plans, restores and backups etc. are picky and often I need to maintain an environment from the correct tool version. I have not had an issue with having several versions installed as long as I install them in the correct order (although I am not even sure that is necessary). Tell the desktop guys to trust the DBA. 😉

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply