Skip to content

Commit d6afad5

Browse files
Add link to SQL Always On white paper (#489)
1 parent 4bb7ae4 commit d6afad5

File tree

1 file changed

+3
-3
lines changed
  • docs/solutions/sql_server_always_on_availability_groups

1 file changed

+3
-3
lines changed

docs/solutions/sql_server_always_on_availability_groups/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@
99

1010
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.
1111

12+
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.
13+
1214
The template is configured by modifying the variables contained in two files:
1315

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

2527
Some items of note:
2628

27-
- 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.
29+
- 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.
2830
- 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
2931
- 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.
3032
- Do not edit any of the files other than configuration.tf and sql.tf. Look, but touch at your own peril.
@@ -37,6 +39,4 @@ Some items of note:
3739

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

40-
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).
41-
4242
Enjoy and happy SQL'ing!

0 commit comments

Comments
 (0)