Code Monkey home page Code Monkey logo

cfn-ps-microsoft-sql-fci-fsx's Introduction

SQL Server Failover Cluster Instance on AWS—Quick Start

For architectural details, step-by-step instructions, and customization options, see the deployment guide.

To post feedback, submit feature ideas, or report bugs, use the Issues section of this GitHub repo.

To submit code for this Quick Start, see the AWS Quick Start Contributor's Kit.

cfn-ps-microsoft-sql-fci-fsx's People

Contributors

davmayd avatar vsnyc avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

cfn-ps-microsoft-sql-fci-fsx's Issues

Duplicate DNS Records Created in Active Directory

Summary:

When deploying this solution against an existing managed Active Directory there are several DNS records created in Active Directory to point to the newly created instances. There is are 2 records created for the FCI with identical names which point to the 3rd IP/ENI of each EC2 instance. One of these records points to the node which has the MSSQLSERVER role active, and the other record points to the standby instance. This causes DNS queries to the FCI to fail 50% of the time since the second instance is not running the MSSQLSERVER role in the Failover Cluster.

Details:
The final step of the SSM automation document created by the cloudformation template is called CompleteFCI. This step takes a parameter from the automation document called SqlFSxFCIName which gets passed as -FCIName {{SqlFSxFCIName}}. When the cluster is created against an existing managed AD it creates the following records:

  • 2 records: 1 record pointing to the primary private IP of each EC2 instance
  • 1 record pointing to the WFC
  • 2 records named from {{SqlFSxFCIName}} with identical names, pointing to the 3rd IP of each of the 2 EC2 instances 3rd IP/ENI. The name of this record is the name to connect to the DB in SQL Server Management Studio, as well as the DNS name to connect to SQL Server

In the Windows Failover Cluster Manager, the first instance is assigned the MSSQLSERVER role, while the second instance is not(active/passive). Because of this DNS queries to {{SqlFSxFCIName}} will hit the standby instance 50% of the time.

Deployment guide feedback

Section heading:
Documentation issue description:

The footer in the article doesn't display the current year:

"Privacy | Site terms | © {current-year}, Amazon Web Services, Inc. or its affiliates. All rights reserved."

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.