Does restarting the SQL Services (on the machine) clear the server cache (for things like query plans and statistics)?What reasons are there to stop the SQL Server?Why did a SQL Server Restart roll-back seemingly committed transactions?KILLED/ROLLBACK query doesn't stop runningRollback taking foreverSQL Server 2008 R2 - Service shutdown - what with running stored procedures?What load does SQL Server Reporting Services (SSRS) have on the server?Why SQL Server installs multiple services for AS and RS, but only one for IS?Does SQL Server cache data results for DAO?Change SQL Server settings without restarting servicesDoes restoring database clear buffer cache and stored proc cacheConnecting a standalone Microsoft R Server to a SQL Server with R Services and a SQL Server without R ServicesCan the plan-cache and/or statistics be copied from one instance to anotherSQL Server 2016 All Queries recompile all the time (plan cache corruption?)Plan Cache: Why are multiple plans cached for this stored procedure in SQL ServerHow does SQL Server determine how much memory to allocate to Data cache
How large is a Globe of Invulnerability cast by a Large creature?
My parents are Afghan
How to get the decimal part of a number in apex
What's weird about Proto-Indo-European Stops?
Make me a minimum magic sum
And now you see it
Where do 5 or more U.S. counties meet in a single point?
If quadruped mammals evolve to become bipedal will their breast or nipple change position?
What's the role of the Receiver/Transmitter in Avengers Endgame?
What detail can Hubble see on Mars?
Appropriate age to involve kids in life changing decisions
How can I finally understand the confusing modal verb "мочь"?
Bash prompt takes only the first word of a hostname before the dot
Scaling rounded rectangles in Illustrator
Musical Shape on music stand
Clauses with 3 infinitives at the end
My C Drive is full without reason
Is there a reason why Turkey took the Balkan territories of the Ottoman Empire, instead of Greece or another of the Balkan states?
What's the difference between "ricochet" and "bounce"?
An adjective or a noun to describe a very small apartment / house etc
Why is the blank symbol not considered part of the input alphabet of a Turing machine?
Does this website provide consistent translation into Wookiee?
Gift for mentor after his thesis defense?
Explaining intravenous drug abuse to a small child
Does restarting the SQL Services (on the machine) clear the server cache (for things like query plans and statistics)?
What reasons are there to stop the SQL Server?Why did a SQL Server Restart roll-back seemingly committed transactions?KILLED/ROLLBACK query doesn't stop runningRollback taking foreverSQL Server 2008 R2 - Service shutdown - what with running stored procedures?What load does SQL Server Reporting Services (SSRS) have on the server?Why SQL Server installs multiple services for AS and RS, but only one for IS?Does SQL Server cache data results for DAO?Change SQL Server settings without restarting servicesDoes restoring database clear buffer cache and stored proc cacheConnecting a standalone Microsoft R Server to a SQL Server with R Services and a SQL Server without R ServicesCan the plan-cache and/or statistics be copied from one instance to anotherSQL Server 2016 All Queries recompile all the time (plan cache corruption?)Plan Cache: Why are multiple plans cached for this stored procedure in SQL ServerHow does SQL Server determine how much memory to allocate to Data cache
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Does the server cache get wiped (similarly to when you restart the SQL instance / machine) when you only restart the SQL Services themselves?
sql-server sql-server-2008-r2 statistics cache plan-cache
asked 6 hours ago
J.D.J.D.
563414
add a comment |
Does the server cache get wiped (similarly to when you restart the SQL instance / machine) when you only restart the SQL Services themselves?
sql-server sql-server-2008-r2 statistics cache plan-cache
asked 6 hours ago
J.D.J.D.
563414
add a comment |
Does the server cache get wiped (similarly to when you restart the SQL instance / machine) when you only restart the SQL Services themselves?
sql-server sql-server-2008-r2 statistics cache plan-cache
asked 6 hours ago
J.D.J.D.
563414
Does the server cache get wiped (similarly to when you restart the SQL instance / machine) when you only restart the SQL Services themselves?
sql-server sql-server-2008-r2 statistics cache plan-cache
sql-server sql-server-2008-r2 statistics cache plan-cache
asked 6 hours ago
J.D.J.D.
563414
asked 6 hours ago
J.D.J.D.
563414
asked 6 hours ago
J.D.J.D.
563414
asked 6 hours ago
J.D.J.D.
563414
asked 6 hours ago
J.D.J.D.
563414
563414
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Yes it does. Since SQL Server is in charge of maintaining those caches, when you shut down SQL server's services, it releases the memory back to the operating system.
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
1
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
add a comment |
The behavior is no different between restarting the service alone or restarting the service due to rebooting the underlying operating system. Which information is wiped on such a restart?
- Query plans? Yes.
- Table/index data? Yes.
- Statistics? No.
(Query plans, which use statistics, will have to be recompiled, but statistics won't have to get re-created unless there was also some event or condition to trigger that (there are several).)
If you stop the service while a transaction is rolling back, you likely haven't accomplished anything, since rollback may just start again from where it left off (or it may have to start over completely, depending on the type of activity that is getting rolled back).
If you restarted the service because you got impatient waiting for a rollback to complete, that's probably an expensive lesson you'll only have to do one or two times before you stop trying. See:
- Why did a SQL Server Restart roll-back seemingly committed transactions?
- KILLED/ROLLBACK query doesn't stop running
- Rollback taking forever
- SQL Server 2008 R2 - Service shutdown - what with running stored procedures?
- https://dba.stackexchange.com/a/160293/1186
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
1
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
1
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
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%2f237494%2fdoes-restarting-the-sql-services-on-the-machine-clear-the-server-cache-for-th%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes it does. Since SQL Server is in charge of maintaining those caches, when you shut down SQL server's services, it releases the memory back to the operating system.
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
1
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
add a comment |
Yes it does. Since SQL Server is in charge of maintaining those caches, when you shut down SQL server's services, it releases the memory back to the operating system.
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
1
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
add a comment |
Yes it does. Since SQL Server is in charge of maintaining those caches, when you shut down SQL server's services, it releases the memory back to the operating system.
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
Yes it does. Since SQL Server is in charge of maintaining those caches, when you shut down SQL server's services, it releases the memory back to the operating system.
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
answered 5 hours ago
Laughing VergilLaughing Vergil
1,028212
1,028212
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
1
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
add a comment |
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
1
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
Thank you! As a bonus question, do you know if restarting just the services during a query being rolled back could potentially result in the server coming back up in the "recovering" state, or is that only a potential outcome from restarting the whole instance / machine?
– J.D.
5 hours ago
1
1
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
It could, but I don't know if it would. The perpetual rollback is a problem of course, and I have had to do what you are asking about before. The DB did not come back in a recovering state, but I might just have been lucky. Some of the consultant class people, like Brent Ozar's crew or Aaron Bertrand may know for sure.
– Laughing Vergil
5 hours ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
Recovery is only needed on unclean shutdown or with preexisting corruption
– eckes
1 hour ago
add a comment |
The behavior is no different between restarting the service alone or restarting the service due to rebooting the underlying operating system. Which information is wiped on such a restart?
- Query plans? Yes.
- Table/index data? Yes.
- Statistics? No.
(Query plans, which use statistics, will have to be recompiled, but statistics won't have to get re-created unless there was also some event or condition to trigger that (there are several).)
If you stop the service while a transaction is rolling back, you likely haven't accomplished anything, since rollback may just start again from where it left off (or it may have to start over completely, depending on the type of activity that is getting rolled back).
If you restarted the service because you got impatient waiting for a rollback to complete, that's probably an expensive lesson you'll only have to do one or two times before you stop trying. See:
- Why did a SQL Server Restart roll-back seemingly committed transactions?
- KILLED/ROLLBACK query doesn't stop running
- Rollback taking forever
- SQL Server 2008 R2 - Service shutdown - what with running stored procedures?
- https://dba.stackexchange.com/a/160293/1186
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
1
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
1
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
add a comment |
The behavior is no different between restarting the service alone or restarting the service due to rebooting the underlying operating system. Which information is wiped on such a restart?
- Query plans? Yes.
- Table/index data? Yes.
- Statistics? No.
(Query plans, which use statistics, will have to be recompiled, but statistics won't have to get re-created unless there was also some event or condition to trigger that (there are several).)
If you stop the service while a transaction is rolling back, you likely haven't accomplished anything, since rollback may just start again from where it left off (or it may have to start over completely, depending on the type of activity that is getting rolled back).
If you restarted the service because you got impatient waiting for a rollback to complete, that's probably an expensive lesson you'll only have to do one or two times before you stop trying. See:
- Why did a SQL Server Restart roll-back seemingly committed transactions?
- KILLED/ROLLBACK query doesn't stop running
- Rollback taking forever
- SQL Server 2008 R2 - Service shutdown - what with running stored procedures?
- https://dba.stackexchange.com/a/160293/1186
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
1
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
1
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
add a comment |
The behavior is no different between restarting the service alone or restarting the service due to rebooting the underlying operating system. Which information is wiped on such a restart?
- Query plans? Yes.
- Table/index data? Yes.
- Statistics? No.
(Query plans, which use statistics, will have to be recompiled, but statistics won't have to get re-created unless there was also some event or condition to trigger that (there are several).)
If you stop the service while a transaction is rolling back, you likely haven't accomplished anything, since rollback may just start again from where it left off (or it may have to start over completely, depending on the type of activity that is getting rolled back).
If you restarted the service because you got impatient waiting for a rollback to complete, that's probably an expensive lesson you'll only have to do one or two times before you stop trying. See:
- Why did a SQL Server Restart roll-back seemingly committed transactions?
- KILLED/ROLLBACK query doesn't stop running
- Rollback taking forever
- SQL Server 2008 R2 - Service shutdown - what with running stored procedures?
- https://dba.stackexchange.com/a/160293/1186
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
The behavior is no different between restarting the service alone or restarting the service due to rebooting the underlying operating system. Which information is wiped on such a restart?
- Query plans? Yes.
- Table/index data? Yes.
- Statistics? No.
(Query plans, which use statistics, will have to be recompiled, but statistics won't have to get re-created unless there was also some event or condition to trigger that (there are several).)
If you stop the service while a transaction is rolling back, you likely haven't accomplished anything, since rollback may just start again from where it left off (or it may have to start over completely, depending on the type of activity that is getting rolled back).
If you restarted the service because you got impatient waiting for a rollback to complete, that's probably an expensive lesson you'll only have to do one or two times before you stop trying. See:
- Why did a SQL Server Restart roll-back seemingly committed transactions?
- KILLED/ROLLBACK query doesn't stop running
- Rollback taking forever
- SQL Server 2008 R2 - Service shutdown - what with running stored procedures?
- https://dba.stackexchange.com/a/160293/1186
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
edited 5 hours ago
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
answered 5 hours ago
Aaron Bertrand♦Aaron Bertrand
155k18303506
155k18303506
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
1
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
1
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
add a comment |
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
1
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
1
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
Thanks Aaron, insightful as usual! When you say "If you stop the service while a transaction is rolling back, you haven't accomplished anything, rollback will just start again from where it left off" are you saying that's always true or in most cases? If the former, how come when we restarted the services, sp_who2 no longer showed the processes being rolled back (their SPIDs were gone)?
– J.D.
5 hours ago
1
1
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
@J.D. sorry, will should be may. It's possible the rollback was blocked before the restart and after the restart there was nothing blocking it so it was able to complete immediately. Killing the services is just a dangerous and unpredictable game.
– Aaron Bertrand♦
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
Ah gotcha. And agreed, unfortunately it wasn't my choice in this case, but I figured it had the same potential repercussions as an instance restart. Do you know if it's possible for the database to come back up in a "recovering" state as well for just the services being restarted similarly to what can happen when the instance is restarted during a rollback?
– J.D.
5 hours ago
1
1
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
@J.D. Sure, anything is possible if you sever SQL Server's artery. :-) Depending on what else was going on in the database at the time you killed the service, you will have to wait for both redo and undo to complete before the database will be available, and there could be other more catastrophic causes for Recovery Pending specifically.
– Aaron Bertrand♦
5 hours ago
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%2f237494%2fdoes-restarting-the-sql-services-on-the-machine-clear-the-server-cache-for-th%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
