![]() > I'm seriously having to have second thoughts about the decision to move to Azure SQL MI. Make sure that you have a full backup of the database(s) I'm seriously having to have second thoughts about the decision to move to Azure SQL MI. There seems to be a bug in the migration. Killing all the sessions were a riskier approach, so wanted to see if we could at least take the DB offline as it was not a critical DB as theĪlso, the Query store in some of the DB's don't work and the product team seems to be working on it. Having know the issue with the problematic DB, we wanted to either kill all the sessions or take the DB offline. We were stuck for almost 2 hours with none of the DB's responding. None of the applications connecting to other DB's were able to connect. Last week, one of the queries in one of the DB's took way too long and thereby blockedĪll the other DB's. Ever since we have moved the DB's to Azure SQL, we have been having multiple performance issues. We have recently migrated our On-prem SQL DBs to Azure SQL Managed instance. ![]() This can be beneficial to other community members reading this thread. ![]() Please click "Mark as Answer" if it solved your issue and/or "Vote as helpful" if it helped. Loop though the connected users and kill their connections Join master.sysdatabases d (nolock) on p.dbid = d.dbid This script to designed to kill all connections for all users to a specified database. This will show the currently connected SQL server and allow confirmation that the new SQL server database is in use.If our aim is drop all sessions on database, just run below script on database which db session need to drop\kill instead of put the DB into offline or single user mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |