Activity overview
Latest activity by bbrown_GG
In the end we ended up skipping this end-other-sessions step because, on an azure managed instance, its value was determined to be less than the potential harm. Details: We considered creating scripts for finding and ending/killing existing sessions for any user other than the one running the upgrade. But those commands could run into problems(deadlocks) with the managed-instance processes which, well, manage the db. A lock up of that type would result in a locked database that could not be fixed by ourselves, only by Azure support because only they can access the OS running the SQL server (this is the downside of the managed instance concept). The risk in skipping this 'end-other-sessions' step is that a table access deadlock occurs, which would be annoying, but wouldn't take down the whole db, and should be fixable by ourselves without needing OS level access and thus Azure support. / comments
In the end we ended up skipping this end-other-sessions step because, on an azure managed instance, its value was determined to be less than the potential harm.Details:We considered creating script...
Hello Kendra, thank you for the quick and detailed response. I did see that restricted user mode is not an option in Managed Instances. The requirement to kill active transactions is simply a long standing preferred practice on this project, used with maintenance windows at deployment time. It's been there for years and I'm not personally aware of a the specific pattern requiring it- which doesn't mean there isn't one. I don't have direct access to the db in question to check its options. Possibly this is simply a heavy handed way to avoid deployment time problems. I can revisit the 'offline' practice with the stakeholders, but of course they will want to know what the options for achieving a safe deployment are (online vs offline vs ?) and the pros and cons of each option. Does Redgate have recommendations or best practices for when and how to run the migrations generated by Change Automation? (I've skimmed some of the redgate docs, like Automated Deployments , but not seen this topic covered) (FYI: while I know how to query in SQL and look up concepts I would not call myself and dba and we don't have a dba directly on staff) After looking at the set options page with termination clauses you linked to I see why you warn that it's a hacky solution- we would be toggling a setting we don't need like 'change_tracking_option' back and forth which would have side effects. Thanks, -Ben / comments
Hello Kendra, thank you for the quick and detailed response.I did see that restricted user mode is not an option in Managed Instances. The requirement to kill active transactions is simply a long ...