locked
Licence for SQL Server 2014 Std DC and DR setup RRS feed

  • Question

  • Hi,

    We have SQL Server 2014 Standard Edition (64-bit) 20 core licence. We are implementing DC and DR setup using Veritas Volume replicator

    DC server:
    Windows Server 2012 , 2 processor, each processor with 10 cores = 20 cores

    DR server:
    Windows Server 2008 R2 , 2 processor, each processor with 8 cores = 16 cores

    SQL Server 2014 Standard Edition is installed on both machine with same licence 

    DC server will be production server.

    With the help of Veritas Volume replicator the data and log file will be replicated to DR server.

    DR server will used be once in a 2/3 month for DR-Drill purpose/check data replicated properly and for Disaster recovery purpose

    Suppose SQL Server is purchase with Software Assurance (Failover server) then whether separate licence is needed at DR server for SQL Server 2014 Standard Edition because data is not replicated via SQL server replication technology(Clustering, Always on, Mirroring/Log Shipping), its replicated by Veritas or same licence of SQL Server can be continued at DR.

    Regards,

    Nikhil P Desai

    Saturday, February 6, 2016 3:34 PM

Answers

  • This forum is for technical questions rather than licensing.  For questions regarding pricing and licensing, contact a Microsoft sales partner or licensing expert. Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist.

    Dan Guzman, Data Platform MVP, http://www.dbdelta.com

    Saturday, February 6, 2016 4:15 PM
  • Nikhil,

    First be very careful when using 3rd party replication tools/ SAN mirroring or the like that it supports transactionally consistent replication of disks -it is critically important that all disks used by a database are synchronised as a unit otherwise one might fall behind the other and result in data-loss (for instance a recorded checkpoint in tlog might not correlate with the hardened data in the datafile). From the quick look at the Veritas info I can see there is a level of support in SQL Server but it looks like all volume activity must be stopped to me. Personally I think that alone makes the solution pointless and you should investigate log shipping instead which is less painless, and the live SQL instance does not need to be stopped.

    I guess I would echo Dan's statement about licensing and getting the definitive from the horses mouth -but from what you have said, it is my understanding that SA would allow you 30day grace period to failover/back (assuming failure) before licensing of the DR instance was an issue. Bear in mind that the DR instance could not be used as a secondary instance for reporting or anything else. As a rule of thumb the mechanism you use for DR is irrelevant to MS, and they are actually more concerned about the use of the DR Instance while it lives in DR.


    Regards,
    Mark Broadbent.
    Microsoft Certified Master | Microsoft Data Platform MVP
    Contact me through twitter | blog | sqlcloud


    Please click "Propose as answer" if a post solves your problem
    or/and vote the post up if it's been helpful.

    Interested in attending a free training? Why not attend SQLSaturday Cambridge and SharePoint Saturday Cambridge? And why not check out my Ultimate Training Resources Page?

    Tuesday, February 9, 2016 12:34 PM

All replies

  • This forum is for technical questions rather than licensing.  For questions regarding pricing and licensing, contact a Microsoft sales partner or licensing expert. Call (1-800-426-9400), Monday through Friday, 6:00 AM to 6:00 PM PST to speak directly to Microsoft licensing specialist.

    Dan Guzman, Data Platform MVP, http://www.dbdelta.com

    Saturday, February 6, 2016 4:15 PM
  • Nikhil,

    First be very careful when using 3rd party replication tools/ SAN mirroring or the like that it supports transactionally consistent replication of disks -it is critically important that all disks used by a database are synchronised as a unit otherwise one might fall behind the other and result in data-loss (for instance a recorded checkpoint in tlog might not correlate with the hardened data in the datafile). From the quick look at the Veritas info I can see there is a level of support in SQL Server but it looks like all volume activity must be stopped to me. Personally I think that alone makes the solution pointless and you should investigate log shipping instead which is less painless, and the live SQL instance does not need to be stopped.

    I guess I would echo Dan's statement about licensing and getting the definitive from the horses mouth -but from what you have said, it is my understanding that SA would allow you 30day grace period to failover/back (assuming failure) before licensing of the DR instance was an issue. Bear in mind that the DR instance could not be used as a secondary instance for reporting or anything else. As a rule of thumb the mechanism you use for DR is irrelevant to MS, and they are actually more concerned about the use of the DR Instance while it lives in DR.


    Regards,
    Mark Broadbent.
    Microsoft Certified Master | Microsoft Data Platform MVP
    Contact me through twitter | blog | sqlcloud


    Please click "Propose as answer" if a post solves your problem
    or/and vote the post up if it's been helpful.

    Interested in attending a free training? Why not attend SQLSaturday Cambridge and SharePoint Saturday Cambridge? And why not check out my Ultimate Training Resources Page?

    Tuesday, February 9, 2016 12:34 PM