SQL server license swithching from Production license to MSDN version.

  • Currently, we are running Production license versions of MS SQL Server. However, given the costs, we want to switch back to MSDN version since the same features are available on MSDN as well.

    Can someone help me in terms of either switching these licenses OR providing steps/directions to perform this.

  • Is this for a production server?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • If you are using these servers for development or testing, then you can use MSDN. If these are used by clients/customers with real data that your company/organization uses, then no, you cannot use MSDN.

  • We have made a product and deployed on cloud with production license of sql server. since we dont have the client in order to minimise the cost we need to have MSDN version now.Later if anty client comes then we can change it again to production SQL server and pay to microsoft. So is there anyway we can change from production licensed version of SQL server to MSDN without uninstalling it? Both are Enterprise edition.

  • SanjeevBaranwal (5/25/2014)


    We have made a product and deployed on cloud with production license of sql server. since we dont have the client in order to minimise the cost we need to have MSDN version now.Later if anty client comes then we can change it again to production SQL server and pay to microsoft. So is there anyway we can change from production licensed version of SQL server to MSDN without uninstalling it? Both are Enterprise edition.

    Heh... call Microsoft and ask them. You'll kill two birds with one stone that way. You'll first find out if your intentions are legally supported and, if they are, then you'll find out how to do it. 😉

    --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)
    Intro to Tally Tables and Functions

  • Keep in mind that MSDN is a per-user license. Only the person, to which the subscription is registered can use the software. If you have a group working on a project, they would each need their own MSDN subscription.

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

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