talk-data.com

Ook in November weer een meetup! Locatie nog vast te stellen (suggesties uiteraard welkom), de speakers hebben inmiddels toegezegd! Hugo neemt ons mee in de prachtige wereld van de execution plans: You have learned the relevance of execution plans. You know where to find them, and you’ve been taught the basics of how to read them. You’ve looked at some of the clean, simple execution plans that presenters used in classroom training, or at conferences, and you feel confident that you can work with them. And then you get your first problem query at your workplace, you look at its execution plan, and you just want to crawl under a rock and cry.

Real code is much more complicated than demo code. Real code translates to large, complex, and often messy execution plans. The principles of reading execution plans still apply, but the plan is large and messy and you struggle where to even begin.

If your query uses a lot of I/O, then which operators are to blame? If your query uses a lot of memory, then what area is responsible? What are some things you should always look at?

Knowing the root cause of a problem can help find a cure. Knowing where to look in a large execution plan can help you find that root cause faster!

Rob gaat dieper in op de security van Azure SQL door het gebruik van Defender: Your work for a company with much exposure in the market. You have setup several things like auditing for being able to notice that something happened to the data. Microsoft Defender for Windows is running. For Legal reasons they require more. They want you to be able to block access when someone tries to get into your system.

The company stakeholder selected a tool for this.. Defender for SQL. Choice is made upon the fact that it combines protection of data in Azure and on Premise. The requirements made up also include things like to protect only certain systems. A wish of the stakeholder is also to include the audit data in the same portal.

How does Defender for SQL work? What is the reaction time. You also struggle about the fact to do it selectively. Can this be done? How to identify data from Premise Cloud in the same Portal? Can we use this data with more solutions? Let me help you getting on the road.