Installing SQL Server with Virtual Account / (managed local accounts)
I am installing SQL Server 2016 by using virtual accounts (which I suppose is managed local accounts) and I cannot see any limitation, drawback of using this simpler method vs. using MSAs.
Would a more experience DBA educate us?
My understanding is that: as long as you do not have any cross-server operations, you are fine. I will not cross servers, but I will cross SQL SERVER INSTANCES (on the same server). Are there any issues that I may face?
I've read these resources and another similar question.
sql-server sql-server-2012 sql-server-2016
edited Apr 13 '17 at 12:43
Community♦
1
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am installing SQL Server 2016 by using virtual accounts (which I suppose is managed local accounts) and I cannot see any limitation, drawback of using this simpler method vs. using MSAs.
Would a more experience DBA educate us?
My understanding is that: as long as you do not have any cross-server operations, you are fine. I will not cross servers, but I will cross SQL SERVER INSTANCES (on the same server). Are there any issues that I may face?
I've read these resources and another similar question.
sql-server sql-server-2012 sql-server-2016
edited Apr 13 '17 at 12:43
Community♦
1
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am installing SQL Server 2016 by using virtual accounts (which I suppose is managed local accounts) and I cannot see any limitation, drawback of using this simpler method vs. using MSAs.
Would a more experience DBA educate us?
My understanding is that: as long as you do not have any cross-server operations, you are fine. I will not cross servers, but I will cross SQL SERVER INSTANCES (on the same server). Are there any issues that I may face?
I've read these resources and another similar question.
sql-server sql-server-2012 sql-server-2016
edited Apr 13 '17 at 12:43
Community♦
1
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
I am installing SQL Server 2016 by using virtual accounts (which I suppose is managed local accounts) and I cannot see any limitation, drawback of using this simpler method vs. using MSAs.
Would a more experience DBA educate us?
My understanding is that: as long as you do not have any cross-server operations, you are fine. I will not cross servers, but I will cross SQL SERVER INSTANCES (on the same server). Are there any issues that I may face?
I've read these resources and another similar question.
sql-server sql-server-2012 sql-server-2016
sql-server sql-server-2012 sql-server-2016
edited Apr 13 '17 at 12:43
Community♦
1
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
edited Apr 13 '17 at 12:43
Community♦
1
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
edited Apr 13 '17 at 12:43
Community♦
1
edited Apr 13 '17 at 12:43
Community♦
1
edited Apr 13 '17 at 12:43
Community♦
1
1
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
asked Oct 10 '16 at 0:42
BeginnerDBABeginnerDBA
984
984
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Based on your description, I don't think you'll have any issues with either account type. One important consideration is whether you have any internal/corporate or external compliance requirements with regards to the service account used by databases.
Depending on the actual policy or compliance requirement, you might find explicit wordings about password management which doesn't exist with VAs. Real security impact is almost never the issue as most of these policies (that I've worked with anyway) are either really dated or written by a "general IT professional" or both. Trying to convince whoever manages these policies or the auditors has never worked for me. Just educating them on how VAs work can be an exercise in futility.
If you aren't affected by such policies/requirements and are unlikely to be in the foreseeable future then you'll be fine with VAs. Else, you're pretty much pushed down the path of MSA or some other form of human/tool managed account.
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
add a comment |
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%2f151830%2finstalling-sql-server-with-virtual-account-managed-local-accounts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Based on your description, I don't think you'll have any issues with either account type. One important consideration is whether you have any internal/corporate or external compliance requirements with regards to the service account used by databases.
Depending on the actual policy or compliance requirement, you might find explicit wordings about password management which doesn't exist with VAs. Real security impact is almost never the issue as most of these policies (that I've worked with anyway) are either really dated or written by a "general IT professional" or both. Trying to convince whoever manages these policies or the auditors has never worked for me. Just educating them on how VAs work can be an exercise in futility.
If you aren't affected by such policies/requirements and are unlikely to be in the foreseeable future then you'll be fine with VAs. Else, you're pretty much pushed down the path of MSA or some other form of human/tool managed account.
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
add a comment |
Based on your description, I don't think you'll have any issues with either account type. One important consideration is whether you have any internal/corporate or external compliance requirements with regards to the service account used by databases.
Depending on the actual policy or compliance requirement, you might find explicit wordings about password management which doesn't exist with VAs. Real security impact is almost never the issue as most of these policies (that I've worked with anyway) are either really dated or written by a "general IT professional" or both. Trying to convince whoever manages these policies or the auditors has never worked for me. Just educating them on how VAs work can be an exercise in futility.
If you aren't affected by such policies/requirements and are unlikely to be in the foreseeable future then you'll be fine with VAs. Else, you're pretty much pushed down the path of MSA or some other form of human/tool managed account.
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
add a comment |
Based on your description, I don't think you'll have any issues with either account type. One important consideration is whether you have any internal/corporate or external compliance requirements with regards to the service account used by databases.
Depending on the actual policy or compliance requirement, you might find explicit wordings about password management which doesn't exist with VAs. Real security impact is almost never the issue as most of these policies (that I've worked with anyway) are either really dated or written by a "general IT professional" or both. Trying to convince whoever manages these policies or the auditors has never worked for me. Just educating them on how VAs work can be an exercise in futility.
If you aren't affected by such policies/requirements and are unlikely to be in the foreseeable future then you'll be fine with VAs. Else, you're pretty much pushed down the path of MSA or some other form of human/tool managed account.
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
Based on your description, I don't think you'll have any issues with either account type. One important consideration is whether you have any internal/corporate or external compliance requirements with regards to the service account used by databases.
Depending on the actual policy or compliance requirement, you might find explicit wordings about password management which doesn't exist with VAs. Real security impact is almost never the issue as most of these policies (that I've worked with anyway) are either really dated or written by a "general IT professional" or both. Trying to convince whoever manages these policies or the auditors has never worked for me. Just educating them on how VAs work can be an exercise in futility.
If you aren't affected by such policies/requirements and are unlikely to be in the foreseeable future then you'll be fine with VAs. Else, you're pretty much pushed down the path of MSA or some other form of human/tool managed account.
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
answered Oct 10 '16 at 14:07
SQLmojoeSQLmojoe
1,32037
1,32037
add a comment |
add a comment |
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%2f151830%2finstalling-sql-server-with-virtual-account-managed-local-accounts%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
