Should a support incident be opened for every stack dump, or just ones that cause an outage?
Assuming that the stack dump in question can't be mapped to a know issue, if a stack dump doesn't seem to cause a problem and everything is working afterwards, should a support incident be opened for it? Or should incidents be opened only when it causes an outage or loss of functionality?
sql-server
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
add a comment |
Assuming that the stack dump in question can't be mapped to a know issue, if a stack dump doesn't seem to cause a problem and everything is working afterwards, should a support incident be opened for it? Or should incidents be opened only when it causes an outage or loss of functionality?
sql-server
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
This seems very opinion-based.
– Aaron Bertrand♦
6 hours ago
@AaronBertrand I can appreciate your opinion that this might seem opinion-based. But it's not--which approach will result in me not wasting my time and Microsoft's support staff time, while still providing them the information they need to make the product better? It would seem to me there is a definite answer, but perhaps only Microsoft folks know, or someone who's asked them this question.
– Tony Hinkle
6 hours ago
If a stack dump is generated by SQL server, to me its a clear bug that needs to be investigated. Now if the stack dump caused a service interruption for your app and your business that part you have to handle it by proper monitoring and providing better visibility when your service degrades.
– Kin
5 hours ago
3rd party modules, detouring, heap corruption, etc., can all have stack dumps generated by SQL server but SQL Server isn't the cause... so it's not quite 100% on that.
– Sean Gallardy
5 hours ago
To be fair, if you read your question, it certainly could be interpreted that you mean "should I open a support incident?" as in "will I get any benefit from doing so?" If you are talking about more altruistic things, like making the product itself better, those should be stated in the question, but it still is something that only Microsoft would know for sure would help them. It probably depends a lot on things that your peers can't answer, like how serious is the issue, how prevalent is it, how easy is it to happen, is there an easy fix, does the team have time right now to investigate...
– Aaron Bertrand♦
4 hours ago
add a comment |
Assuming that the stack dump in question can't be mapped to a know issue, if a stack dump doesn't seem to cause a problem and everything is working afterwards, should a support incident be opened for it? Or should incidents be opened only when it causes an outage or loss of functionality?
sql-server
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
Assuming that the stack dump in question can't be mapped to a know issue, if a stack dump doesn't seem to cause a problem and everything is working afterwards, should a support incident be opened for it? Or should incidents be opened only when it causes an outage or loss of functionality?
sql-server
sql-server
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
asked 6 hours ago
Tony HinkleTony Hinkle
2,4801422
2,4801422
This seems very opinion-based.
– Aaron Bertrand♦
6 hours ago
@AaronBertrand I can appreciate your opinion that this might seem opinion-based. But it's not--which approach will result in me not wasting my time and Microsoft's support staff time, while still providing them the information they need to make the product better? It would seem to me there is a definite answer, but perhaps only Microsoft folks know, or someone who's asked them this question.
– Tony Hinkle
6 hours ago
If a stack dump is generated by SQL server, to me its a clear bug that needs to be investigated. Now if the stack dump caused a service interruption for your app and your business that part you have to handle it by proper monitoring and providing better visibility when your service degrades.
– Kin
5 hours ago
3rd party modules, detouring, heap corruption, etc., can all have stack dumps generated by SQL server but SQL Server isn't the cause... so it's not quite 100% on that.
– Sean Gallardy
5 hours ago
To be fair, if you read your question, it certainly could be interpreted that you mean "should I open a support incident?" as in "will I get any benefit from doing so?" If you are talking about more altruistic things, like making the product itself better, those should be stated in the question, but it still is something that only Microsoft would know for sure would help them. It probably depends a lot on things that your peers can't answer, like how serious is the issue, how prevalent is it, how easy is it to happen, is there an easy fix, does the team have time right now to investigate...
– Aaron Bertrand♦
4 hours ago
add a comment |
This seems very opinion-based.
– Aaron Bertrand♦
6 hours ago
@AaronBertrand I can appreciate your opinion that this might seem opinion-based. But it's not--which approach will result in me not wasting my time and Microsoft's support staff time, while still providing them the information they need to make the product better? It would seem to me there is a definite answer, but perhaps only Microsoft folks know, or someone who's asked them this question.
– Tony Hinkle
6 hours ago
If a stack dump is generated by SQL server, to me its a clear bug that needs to be investigated. Now if the stack dump caused a service interruption for your app and your business that part you have to handle it by proper monitoring and providing better visibility when your service degrades.
– Kin
5 hours ago
3rd party modules, detouring, heap corruption, etc., can all have stack dumps generated by SQL server but SQL Server isn't the cause... so it's not quite 100% on that.
– Sean Gallardy
5 hours ago
To be fair, if you read your question, it certainly could be interpreted that you mean "should I open a support incident?" as in "will I get any benefit from doing so?" If you are talking about more altruistic things, like making the product itself better, those should be stated in the question, but it still is something that only Microsoft would know for sure would help them. It probably depends a lot on things that your peers can't answer, like how serious is the issue, how prevalent is it, how easy is it to happen, is there an easy fix, does the team have time right now to investigate...
– Aaron Bertrand♦
4 hours ago
This seems very opinion-based.
– Aaron Bertrand♦
6 hours ago
This seems very opinion-based.
– Aaron Bertrand♦
6 hours ago
@AaronBertrand I can appreciate your opinion that this might seem opinion-based. But it's not--which approach will result in me not wasting my time and Microsoft's support staff time, while still providing them the information they need to make the product better? It would seem to me there is a definite answer, but perhaps only Microsoft folks know, or someone who's asked them this question.
– Tony Hinkle
6 hours ago
@AaronBertrand I can appreciate your opinion that this might seem opinion-based. But it's not--which approach will result in me not wasting my time and Microsoft's support staff time, while still providing them the information they need to make the product better? It would seem to me there is a definite answer, but perhaps only Microsoft folks know, or someone who's asked them this question.
– Tony Hinkle
6 hours ago
If a stack dump is generated by SQL server, to me its a clear bug that needs to be investigated. Now if the stack dump caused a service interruption for your app and your business that part you have to handle it by proper monitoring and providing better visibility when your service degrades.
– Kin
5 hours ago
If a stack dump is generated by SQL server, to me its a clear bug that needs to be investigated. Now if the stack dump caused a service interruption for your app and your business that part you have to handle it by proper monitoring and providing better visibility when your service degrades.
– Kin
5 hours ago
3rd party modules, detouring, heap corruption, etc., can all have stack dumps generated by SQL server but SQL Server isn't the cause... so it's not quite 100% on that.
– Sean Gallardy
5 hours ago
3rd party modules, detouring, heap corruption, etc., can all have stack dumps generated by SQL server but SQL Server isn't the cause... so it's not quite 100% on that.
– Sean Gallardy
5 hours ago
To be fair, if you read your question, it certainly could be interpreted that you mean "should I open a support incident?" as in "will I get any benefit from doing so?" If you are talking about more altruistic things, like making the product itself better, those should be stated in the question, but it still is something that only Microsoft would know for sure would help them. It probably depends a lot on things that your peers can't answer, like how serious is the issue, how prevalent is it, how easy is it to happen, is there an easy fix, does the team have time right now to investigate...
– Aaron Bertrand♦
4 hours ago
To be fair, if you read your question, it certainly could be interpreted that you mean "should I open a support incident?" as in "will I get any benefit from doing so?" If you are talking about more altruistic things, like making the product itself better, those should be stated in the question, but it still is something that only Microsoft would know for sure would help them. It probably depends a lot on things that your peers can't answer, like how serious is the issue, how prevalent is it, how easy is it to happen, is there an easy fix, does the team have time right now to investigate...
– Aaron Bertrand♦
4 hours ago
add a comment |
1 Answer
1
active
oldest
votes
It's fairly cut and dry: If you want to actually work on the issue, collect data, uninstall/reinstall, isolate, test, potentially provide more dumps, potentially use things like appverifier and debugdiag or have a valid repro, then by all means open a ticket so it can be looked into and worked on.
If you just want to ship off a stack dump, with no other data, and have someone look at it in a vacuum, then I would not open a ticket as it'll have no traction and go nowhere. Neither party will be happy.
That's the short and sweet version.
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
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%2f230165%2fshould-a-support-incident-be-opened-for-every-stack-dump-or-just-ones-that-caus%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
It's fairly cut and dry: If you want to actually work on the issue, collect data, uninstall/reinstall, isolate, test, potentially provide more dumps, potentially use things like appverifier and debugdiag or have a valid repro, then by all means open a ticket so it can be looked into and worked on.
If you just want to ship off a stack dump, with no other data, and have someone look at it in a vacuum, then I would not open a ticket as it'll have no traction and go nowhere. Neither party will be happy.
That's the short and sweet version.
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
add a comment |
It's fairly cut and dry: If you want to actually work on the issue, collect data, uninstall/reinstall, isolate, test, potentially provide more dumps, potentially use things like appverifier and debugdiag or have a valid repro, then by all means open a ticket so it can be looked into and worked on.
If you just want to ship off a stack dump, with no other data, and have someone look at it in a vacuum, then I would not open a ticket as it'll have no traction and go nowhere. Neither party will be happy.
That's the short and sweet version.
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
add a comment |
It's fairly cut and dry: If you want to actually work on the issue, collect data, uninstall/reinstall, isolate, test, potentially provide more dumps, potentially use things like appverifier and debugdiag or have a valid repro, then by all means open a ticket so it can be looked into and worked on.
If you just want to ship off a stack dump, with no other data, and have someone look at it in a vacuum, then I would not open a ticket as it'll have no traction and go nowhere. Neither party will be happy.
That's the short and sweet version.
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
It's fairly cut and dry: If you want to actually work on the issue, collect data, uninstall/reinstall, isolate, test, potentially provide more dumps, potentially use things like appverifier and debugdiag or have a valid repro, then by all means open a ticket so it can be looked into and worked on.
If you just want to ship off a stack dump, with no other data, and have someone look at it in a vacuum, then I would not open a ticket as it'll have no traction and go nowhere. Neither party will be happy.
That's the short and sweet version.
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
answered 5 hours ago
Sean GallardySean Gallardy
16k22548
16k22548
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%2f230165%2fshould-a-support-incident-be-opened-for-every-stack-dump-or-just-ones-that-caus%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
This seems very opinion-based.
– Aaron Bertrand♦
6 hours ago
@AaronBertrand I can appreciate your opinion that this might seem opinion-based. But it's not--which approach will result in me not wasting my time and Microsoft's support staff time, while still providing them the information they need to make the product better? It would seem to me there is a definite answer, but perhaps only Microsoft folks know, or someone who's asked them this question.
– Tony Hinkle
6 hours ago
If a stack dump is generated by SQL server, to me its a clear bug that needs to be investigated. Now if the stack dump caused a service interruption for your app and your business that part you have to handle it by proper monitoring and providing better visibility when your service degrades.
– Kin
5 hours ago
3rd party modules, detouring, heap corruption, etc., can all have stack dumps generated by SQL server but SQL Server isn't the cause... so it's not quite 100% on that.
– Sean Gallardy
5 hours ago
To be fair, if you read your question, it certainly could be interpreted that you mean "should I open a support incident?" as in "will I get any benefit from doing so?" If you are talking about more altruistic things, like making the product itself better, those should be stated in the question, but it still is something that only Microsoft would know for sure would help them. It probably depends a lot on things that your peers can't answer, like how serious is the issue, how prevalent is it, how easy is it to happen, is there an easy fix, does the team have time right now to investigate...
– Aaron Bertrand♦
4 hours ago