When your SQL Server is critically injured you need a first responder kit to help you diagnose the problem and apply emergency aid. In this session, Kendra Little introduces you to invaluable tools and techniques for triaging an emergency. If you have one year’s experience with database administration, this half-hour session will set you up to triage like a pro.
The Women in Technology lunch and panel discussion at the PASS Summit last week had a great topic: negotiation. When it came time to Q & A, I knew exactly what topic I wanted to introduce. How Should You Prepare to Ask for a Raise? It’s funny this was my question, because I don’t need to…
How do you know which indexes to create to improve your database performance? Microsoft Certified Master Kendra Little shows you how to find a missing index, decide on the best index definition, and measure the usefulness of your new index. If you know the basics of what a database index does and want to learn the smart way to design indexes, this talk is for you.
There’s a DAC in SQL Server that you should know and love. Sadly, you probably either haven’t met or you’ve forgotten to turn it on.
DAC? What’s That?
First, a little disambiguation. The acronym ‘DAC’ is too popular.
I recently presented to the Salem Oregon SQL Server user group. During my visit I heard an interesting story: once upon a time in a land not so far way, a high severity production incident was caused by adding an additional data file to the tempdb database. Multiple Tempdb Data Files: Commonly Recommended Using multiple database…
What do *you* do when your database has a problem with blocking? Most people reach for the “NOLOCK” hint. Bad news: that may introduce other problems, and it doesn’t truly resolve the root problem in your application code. In this video Kendra Little summarizes five big-picture application changes that fight blocking long term.
This 300 level talk is designed for developers and DBAs who understand table structures, index structures, and common query patterns. We're going to keep things general: no demos, just concept discussions.
You want to hire a fantastic DBA or database developer.
You want someone who can hit the ground running, who you can trust to maintain your current system and tune it like a pro. Plus you want someone who can see key improvements, communicate effectively, and drive change in your system.
It's morning standup, and someone says, "It's no big deal, we just need to add a couple of columns. It's already in the build, it works fine."
The next time this happens, stop and say, "Let's take a closer look at that."
