Post reply

Staging or UAT Environment

  • January 19, 2021 at 11:52 am

    Go to Answer

    #3834955

    Hi Experts,

    Currently, we are using the enterprise edition of SQL Server 2014 in our Pre-Prod environment, planning to move it to SQL Server 2019 Developer edition. Will this create any issue in the future wrt to Licensing or issue resolutions.

    We will be using the same exact upgrade plan of Pre-Prod to upgrade production SQL Server 2014 to 2019 migration (Enterprise Edition).

    TIA

     

  • January 19, 2021 at 1:51 pm

    Answer

    #3835037

    If you stop calling it "Pre-Prod" and start calling it "UAT", there will be no question that it's not actually a production environment.  Of course, no part of it can actually be a part of any production application or data processing.

    Our Dev, Staging, and UAT environments are all properly running the Developer's Edition with no licensing issues.

     

    --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)

  • January 20, 2021 at 4:06 am

    #3835323

    Jeff Moden wrote:

    If you stop calling it "Pre-Prod" and start calling it "UAT", there will be no question that it's not actually a production environment.  Of course, no part of it can actually be a part of any production application or data processing.

    Our Dev, Staging, and UAT environments are all properly running the Developer's Edition with no licensing issues.

    Thanks Jeff, Normally we use this environment for the final phase of testing before moving things to Production.

    I am confused whether its my call to decide this change or how & what to inform the management.

    Thanks again Jeff.

  • January 20, 2021 at 4:32 pm

    #3835575

    VastSQL wrote:

    Jeff Moden wrote:

    If you stop calling it "Pre-Prod" and start calling it "UAT", there will be no question that it's not actually a production environment.  Of course, no part of it can actually be a part of any production application or data processing.

    Our Dev, Staging, and UAT environments are all properly running the Developer's Edition with no licensing issues.

    Thanks Jeff, Normally we use this environment for the final phase of testing before moving things to Production.

    I am confused whether its my call to decide this change or how & what to inform the management.

    Thanks again Jeff.

    All of our Dev, Staging, and UAT boxes are legally the SQL Developer Edition.  Just remember that the Developer Edition has all the same features as the SQL Enterprise Edition.  If you're prod box(es) are the SQL Standard Edition, you have to be careful to NOT use any "Enterprise Only" features in the lower environments.

    --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)

  • January 21, 2021 at 5:03 am

    #3835750

    Jeff Moden wrote:

    VastSQL wrote:

    Jeff Moden wrote:

    If you stop calling it "Pre-Prod" and start calling it "UAT", there will be no question that it's not actually a production environment.  Of course, no part of it can actually be a part of any production application or data processing.

    Our Dev, Staging, and UAT environments are all properly running the Developer's Edition with no licensing issues.

    Thanks Jeff, Normally we use this environment for the final phase of testing before moving things to Production.

    I am confused whether its my call to decide this change or how & what to inform the management.

    Thanks again Jeff.

    All of our Dev, Staging, and UAT boxes are legally the SQL Developer Edition.  Just remember that the Developer Edition has all the same features as the SQL Enterprise Edition.  If you're prod box(es) are the SQL Standard Edition, you have to be careful to NOT use any "Enterprise Only" features in the lower environments.

    Thanks  a lot Jeff, Our Productions are all Enterprise.

  • January 21, 2021 at 5:04 pm

    #3835948

    VastSQL wrote:

    I am confused whether its my call to decide this change or how & what to inform the management.

    Sorry, I missed that part.  I would say that it's NOT actually up to the DBA because it involves product licensing and payment.  Yes, you should inform people that their could be a savings by switching to the Developer's Edition but the people paying the bills will need to verify that to "keep the company safe license-wise".

     

    --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)

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

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