Database server administration and Tiering
I work for the an Emergency services group in Australia
I've recently thought to create 3 tiers of database classification
Tier 1 - Is multi Availability Groups and multiple servers - Include AG1 for high security, AG2 high available 1. Updates etc can be applied to servers in this environment in a staged manner
Tier 2 - A single Fail over cluster - this has the production non core services - like reporting services
Tier 3 - Includes the non production environments and maybe fail over clusters for accurate testing
Some things I would envisage being a benefit from this model is
Logging for sensitive data sets can be ramped up on a individual AV Group - inline with the business desires. Testing for Service packs etc can be implemented onto production to get final UAT while having a back out plan
Migration to Cloud based or "as a service" will be less painful.
So my questions are
Would you consider building different Database environments based on security and operational need?
Do you agree with this as a strategy?
Is there a different proffered option ?
How would you sell the concept with Management - given this adds complexity to daily management and implementation resource requirements?
sql-server database-design
add a comment |
I work for the an Emergency services group in Australia
I've recently thought to create 3 tiers of database classification
Tier 1 - Is multi Availability Groups and multiple servers - Include AG1 for high security, AG2 high available 1. Updates etc can be applied to servers in this environment in a staged manner
Tier 2 - A single Fail over cluster - this has the production non core services - like reporting services
Tier 3 - Includes the non production environments and maybe fail over clusters for accurate testing
Some things I would envisage being a benefit from this model is
Logging for sensitive data sets can be ramped up on a individual AV Group - inline with the business desires. Testing for Service packs etc can be implemented onto production to get final UAT while having a back out plan
Migration to Cloud based or "as a service" will be less painful.
So my questions are
Would you consider building different Database environments based on security and operational need?
Do you agree with this as a strategy?
Is there a different proffered option ?
How would you sell the concept with Management - given this adds complexity to daily management and implementation resource requirements?
sql-server database-design
add a comment |
I work for the an Emergency services group in Australia
I've recently thought to create 3 tiers of database classification
Tier 1 - Is multi Availability Groups and multiple servers - Include AG1 for high security, AG2 high available 1. Updates etc can be applied to servers in this environment in a staged manner
Tier 2 - A single Fail over cluster - this has the production non core services - like reporting services
Tier 3 - Includes the non production environments and maybe fail over clusters for accurate testing
Some things I would envisage being a benefit from this model is
Logging for sensitive data sets can be ramped up on a individual AV Group - inline with the business desires. Testing for Service packs etc can be implemented onto production to get final UAT while having a back out plan
Migration to Cloud based or "as a service" will be less painful.
So my questions are
Would you consider building different Database environments based on security and operational need?
Do you agree with this as a strategy?
Is there a different proffered option ?
How would you sell the concept with Management - given this adds complexity to daily management and implementation resource requirements?
sql-server database-design
I work for the an Emergency services group in Australia
I've recently thought to create 3 tiers of database classification
Tier 1 - Is multi Availability Groups and multiple servers - Include AG1 for high security, AG2 high available 1. Updates etc can be applied to servers in this environment in a staged manner
Tier 2 - A single Fail over cluster - this has the production non core services - like reporting services
Tier 3 - Includes the non production environments and maybe fail over clusters for accurate testing
Some things I would envisage being a benefit from this model is
Logging for sensitive data sets can be ramped up on a individual AV Group - inline with the business desires. Testing for Service packs etc can be implemented onto production to get final UAT while having a back out plan
Migration to Cloud based or "as a service" will be less painful.
So my questions are
Would you consider building different Database environments based on security and operational need?
Do you agree with this as a strategy?
Is there a different proffered option ?
How would you sell the concept with Management - given this adds complexity to daily management and implementation resource requirements?
sql-server database-design
sql-server database-design
asked 2 mins ago
FatherosamFatherosam
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233450%2fdatabase-server-administration-and-tiering%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233450%2fdatabase-server-administration-and-tiering%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown