- \n
- How many do you need?<\/li>\n
- Will they be in the same data centre or different ones?\n
- \n
- Check the network latency<\/li>\n<\/ul>\n<\/li>\n
- Will they be accessible for reading?<\/li>\n<\/ul>\n
Next, nodes<\/strong>:<\/p>\n
- \n
- Will the nodes be in the same sub-net or in two sub-nets?<\/li>\n<\/ul>\n
And finally, databases<\/strong>:<\/p>\n
- \n
- How many do you need?<\/li>\n
- How big are they going to be?<\/li>\n
- What are the planned activities for the databases?<\/li>\n<\/ul>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section bb_built=”1″ module_id=”serviceaccounts” _builder_version=”3.12.2″ background_color=”#ededed” custom_padding=”0|0px|0|0px|false|false” prev_background_color=”#ffffff” next_background_color=”#ffffff” inner_width=”auto” inner_max_width=”1080px”][et_pb_row _builder_version=”3.0.48″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” width=”80%” max_width=”1080px”][et_pb_column type=”4_4″ custom_padding__hover=”|||” custom_padding=”|||”][et_pb_text ol_item_indent=”5px” _builder_version=”3.17.6″ header_2_text_color=”#e05206″ header_6_text_color=”#0078d4″ text_orientation=”left”]<\/p>\n
#2. NETWORK<\/h2>\n
Here are the key requirements to send over and discuss with the network team:<\/p>\n
- \n
- 1 IP dedicated by sub-net for each node<\/li>\n
- 1 IP dedicated to the failover cluster<\/li>\n<\/ul>\n
For each\u00a0SQL Server Always On Availability Group (AAG) you’ll also need:<\/p>\n
- \n
- 1 port number for the listener<\/li>\n
- 1 endpoint port number (the default is 5022)<\/li>\n
- A share folder in which the SQL engine service account has read\/write permissions (used to initialise the replication when adding a database in an Always On AG)<\/li>\n<\/ul>\n
All ticked off? Great, let’s have a look at DNS and IP addresses next.<\/p>\n
![\"DNS](\"http:\/\/content.n4stack.io\/wp-content\/uploads\/2018\/10\/DNS-IP-Addresses-1024x241.jpg\")
<\/p>\n[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section bb_built=”1″ module_id=”installation” _builder_version=”3.12.2″ custom_padding=”0|0px|0|0px|false|false” prev_background_color=”#ededed” next_background_color=”#ededed” inner_width=”auto” inner_max_width=”1080px”][et_pb_row _builder_version=”3.0.48″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” width=”80%” max_width=”1080px”][et_pb_column type=”4_4″ custom_padding__hover=”|||” custom_padding=”|||”][et_pb_text _builder_version=”3.17.6″ header_2_text_color=”#e05206″ text_orientation=”left”]<\/p>\n
#3. SERVICE ACCOUNTS<\/h2>\n
Quick reminder as we move onto service accounts \u2013 the account that runs SQL Services\u00a0must<\/strong>\u00a0be a domain account, not the local machine service account, as it needs to be able to access every replica. Also, this account must belong to the administrators group on each of the replicas. So, for my service account checklist:<\/p>\n
- \n
- Create a SQL engine service account and generate a password for SQL Server<\/li>\n
- Create a SQL agent service account and generate a password for SQL Server<\/li>\n<\/ul>\n
Before we jump to our next step I\u2019ve got a question for you \u2013 have you installed any SSIS, SSAS or SSRS service accounts? If \u2018yes\u2019 you\u2019ll need to create additional SQL service accounts for each one.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section][et_pb_section bb_built=”1″ module_id=”servers” _builder_version=”3.12.2″ background_color=”#ededed” custom_padding=”0|0px|0|0px|false|false” prev_background_color=”#ffffff” next_background_color=”#ffffff” inner_width=”auto” inner_max_width=”1080px”][et_pb_row _builder_version=”3.0.48″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” width=”80%” max_width=”1080px”][et_pb_column type=”4_4″ custom_padding__hover=”|||” custom_padding=”|||”][et_pb_text ul_item_indent=”5px” ol_item_indent=”5px” _builder_version=”3.12.2″ header_2_text_color=”#e05206″ header_6_text_color=”#e05206″ text_orientation=”left”]<\/p>\n
#4. INSTALLATION & SERVER ADMINISTRATION ACCOUNTS<\/h2>\n
Now let’s take a look at the admin accounts, you\u2019ll need a:<\/p>\n
- \n
- Sysadmin AD account (to manage the servers)<\/li>\n
- Failover cluster account (linked to failover cluster)<\/li>\n<\/ul>\n
Once installed you\u2019ll need to set permissions for your failover cluster account in AS on the folder containing the failover cluster computer object:<\/p>\n
- \n
- Create computer objects<\/li>\n
- Read all properties<\/li>\n<\/ul>\n
If the above two permissions aren\u2019t set, an error will pop up when generating the Always On listener: Create failed for Availability Group Listener.<\/em><\/p>\n
![\"Create](\"http:\/\/content.n4stack.io\/wp-content\/uploads\/2018\/10\/Create-Failed-for-Availability-Group-Listener.jpg\")
<\/p>\nSource: Microsoft<\/a><\/em><\/p>\n
Here\u2019s where I give you two options \u2013 there\u2019s no right or wrong way to generate the listener, so opt for whichever makes the most sense to you.<\/p>\n
You can pre-stage the listener:<\/h6>\n
- \n
- Find the OU with the CNO in it<\/li>\n
- Create a computer object, name it your DNS listener name<\/li>\n
- Set the security on the new VCO and give the CNO full control over it (full control isn’t required but the list of needs is fairly long so full control is simpler)<\/li>\n
- Create the listener through SSMS\/TSQL\/Powershell<\/li>\n<\/ul>\n
Or you can allow the cluster to create the listener itself:<\/h6>\n
- \n
- Give the CNO: create computer objects, list properties, read properties, write properties over the OU it resides in<\/li>\n
- Create the listener through SSMS\/TSQL\/Powershell<\/li>\n<\/ul>\n
- Will the nodes be in the same sub-net or in two sub-nets?<\/li>\n<\/ul>\n
![\"Storage](\"http:\/\/content.n4stack.io\/wp-content\/uploads\/2018\/10\/Storage.jpg\")
<\/p>\n