Closed potatoqualitee closed 5 years ago
I'll take a look.
When's v1.0 meant to be out the door?
Merci beaucoup! June 1 I'm hoping
Ah, good. For some reason I though it was earlier.
Thinking this through, I think we can break this down into a number of smaller functions that will have some other use:
Set-DbaSqlStartupFlags Start-DbaSqlService Stop-DbaSqlService Start/Stop-DbaClusterInstance
and then the restore is just going to be reusing the existing code.
Ready for testing
I've got this working well with standalone instances. Clusters need more testing.
Would you be happy for me to push this up for others to test? Would add a check for cluster to warn user and force them accept the risk for now?
are ever going to see Restore-DbaSystemDatabase in dbatools?
It is on the roadmap, but not exact time as to when it will be added.
Taken my name off of this one as handing someone a resume generating event speedup tool doesn't sit well with me. Trying to get this to work reliably wasn't happening, and I'd kill clustered instances on a regular basis. I would not want to be supporting this AT ALL. This doesn't work the instance is dead in the water and it's a manual fix, which is the same as doing the restore, so might as well just do it the right way in the first place :)
im gonna go with stuart's recommendation 👍
Is this a feature OR bug:
feature
Details
Hey @Stuart-Moore - would you be able to work on this?
Here are some tutorials:
https://msdn.microsoft.com/en-us/library/ms345408%28SQL.90%29.aspx https://msdn.microsoft.com/en-us/library/ms345408(v=sql.130).aspx
I tried once and then ran out of time because I got caught up trying to offer what was essentially Move-DbaSystemDatabase (which was hell).
Here's what I had when I said F it. I couldn't get it to work consistently enough but I think it only was annoying for the move and not the restore.
Please ignore the bad practices -- this is from 3 years ago.