Skip to content

Add link to SQL Always On white paper #489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2018
Merged

Add link to SQL Always On white paper #489

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/solutions/sql_server_always_on_availability_groups/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@

This Terraform template implements the infrastructure needed to fully deploy an MS SQL Always On cluster across availability domains. The cluster can be spread across either 2 or 3 ADs, depending on your requirements, but cannot be located in a single AD.

This *ONLY* deploys the infrastructure needed to build MS SQL Always On, and *DOES NOT* perform the installation and configuration needed at the operating system. That is covered as an exercise left to the reader in the [Deploying Microsoft SQL Server Always On Availability Groups](https://docs.us-phoenix-1.oraclecloud.com/Content/Resources/Assets/deploy-sql-server-availability-groups.pdf) white paper.

The template is configured by modifying the variables contained in two files:

- configuration.tf - generalized configuration for the environment as a whole.
Expand All @@ -24,7 +26,7 @@ To configure, simply edit these two files, apply values that are appropriate to

Some items of note:

- This has only been tested using Windows 2012 R2 images. The template and accompanying whitepaper has not been deployed using Windows 2016 Datacenter within the OCI environment.
- This has only been tested using Windows 2012 R2 images. The template and accompanying white paper has not been deployed using Windows 2016 Datacenter within the OCI environment.
- The image OCID listed in the configuration.tf file is the one used for testing. You should update this with the image OCID of the latest revision of Windows 2012 R2. For a list of image OCIDs, see https://docs.us-phoenix-1.oraclecloud.com/Content/Resources/Assets/OracleProvidedImageOCIDs.pdf
- If you choose *NOT* to specify an existing compartment in which to deploy MS SQL Always On, one will be created for you. Understand that compartments, once created, *CANNOT* be destroyed.
- Do not edit any of the files other than configuration.tf and sql.tf. Look, but touch at your own peril.
Expand All @@ -37,6 +39,4 @@ Some items of note:

A sample ConfigurationFile.ini file has been included for SQL. Use at your own discretion.

Remember, this *ONLY* deploys the infrastructure needed to build MS SQL Always On, and *DOES NOT* perform the installation and configuration needed at the operating system. That is covered as an exercise left to the reader in the OCI SQL Always On Deployment guide (URL TBD).

Enjoy and happy SQL'ing!