Let's start with the mimosa recipe because it is a good one:
- 1/3 a champagne flute of Orange Juice
- 1/2 oz Don Julio Blanco tequila
- 1/2 oz Gand Marnier Cognac & Orange Liqueur
- fill remaining flute with good champagne like Veuve Clicquot
Let's start with the mimosa recipe because it is a good one:
Josh Luedeman (Twitter | @JoshLuedeman), Neeraj Jhaveri (Twitter | @Neeraj_Jhaveri), Daniel Taylor (Twitter | @DBABulldog), Andres Padilla (Twitter | @nodestreamio), & myself all decided we should submit to the conference. The really amazing part, as much time as we've spent with online we've never all gathered together before. Josh, Neeraj, & I had met pre-covid during work trips, but Andres & Dan had joined our team during the pandemic. Our good friend Bradley Schacht (Twitter | @BradleySchacht) from the Azure Synapse Product Group joined us!
We started out with a nice dinner on Thursday and the in person preparations began for our pre-con DBA 101: A Full Day of Fundamentals. We had a great group of gentlemen that joined us for the day. We covered a lot of basics about SQL Server and the Cloud, specifically Azure, but we made sure people understood how to translate that skill set.
We did a lot of group exercises, starting with building on premise, hybrid, and cloud architectures. Then applying SLA's, RTO, RPO requirements so we could discuss how to configure backups, high availability, and then disaster recovery.
We reviewed basic security within SQL Server which translates to Azure SQL, as well as some basic Identity topics covering AD & AAD. Great group of people and a great way to kick off Friday.
Friday night took us to the SQL Saturday Speaker dinner and then a group activity we had planned together watching the Guardians of the Galaxy 3. No spoilers. Great movie and a really nice send off to the trilogy.
After that we headed back to the hotel, hung out, had some nice conversations, and then went to sleep so we could start the big event, SQL Saturday.
All of us who have been in the community for a while have seen the ups and downs that happened during the pandemic. We all had a lot to deal with in that time, and there were some devastating losses for me personally. Maybe next year I will write about it, but there are some areas that are still to raw for me. I'm sure there are for a lot of people. I tried to remind myself during that time that in the middle of something you cannot see the end, nor can you see the recovery. I held fast to the idea that they would occur.
In the SQL Community I have made so many close deeply personal friendships, that calling people "friends" hardly does justice to what I feel. Of those people Karla & Rodney Landrum are up there at the top. The last time I saw them they came to Orlando to visit. Karla, Rodney, Sue, and myself went to Chef's in the Paris district of Epcot. We also had them over to the house. I cooked, Karla mixed the drinks (which I loved still to this day!) and we had a fantastic time. That was 2019. There is no way we could have known how long it would be until we saw each other again, what we would have encountered. It was all I could do not to breakdown crying as I hugged Karla.I didn't realize she would be there, and the joy I feel even know days removed is palpable. I'm so glad we are having in person events again. I'm so glad I get to see my friends, donate my time, and teach people. If you have a SQL Saturday happening near you, you've got to check them out, I cannot recommend getting involved enough.Here's a little from the blog:
To paraphrase Annie, Deadlocks ARE JUST AWFUL! When they occur, it means one transaction was the victim and rolled back, the other succeeded. You have a couple different ways to monitor them in Azure SQL Managed Instance. Let's review those together.
What is a deadlock? To quote our MS Learn Documentation, "Deadlocks occur when two or more processes or transactions block each other from continuing because each has locked a database resource that the other transaction needs".
In layman's terms a deadlock occurs when two queries are blocking one another and neither could ever complete its transaction. Pretend two people need to use the same door. They cannot fit through at the same time. One must stop and let the other proceeded first. Now add on top of that they both reached for the door knob and grabbed it at the same time, both pulling the door in an opposite direction.
Instead of simply waiting, one must let go of the door knob. In this case the door knob is a table, the hands reaching out are attempting to gain a lock. In SQL Server, all versions of the database engine, this is accomplished by the Lock Manager it uses a process called FIFO, first in first out, to determine who has to let go.
In the case of SQL one transaction is a deadlock victim, it is killed and the transaction is rolled back. So if this is occurring on your system fixing it is very important. First you have to find out if they are occurring, and that's what we will cover in this blog post today!
To read the rest here is the link: Monitoring Deadlocks in Azure SQL Managed Instance.
As always Dear Reader, Thank You for stopping by.
Thanks,
Brad