This week’s question from a reader: “How do I deal with interview questions asking about real-world scenarios when I’ve faked three years of experience on my resume?”
Hear my answer in this 14 minute video.
One of the cool things about Query Store is that you can back it up with the database.
This isn’t perfect for every situation, because you must back up the whole database. If you’ve got a multi-terabyte database, your Query Store isn’t super portable! But still, it’s great to have an option.
Lots of us want to write for TSQL Tuesday, but aren’t always on Twitter at the right time each month to see when the announcement comes out using the #tsql2sday hash tag. And maybe we have an RSS feed set up, but we often get behind on a big pile of posts to read. (Guilty!)
In this episode of “Dear SQL DBA”, I talk about three articles written by members of the SQL Server community on interviewing that I can’t stop thinking about.
I’m glad I picked interviewing as the topic of TSQL Tuesday #93, because people wrote posts chock full of great advice and funny stories. Get ready to learn, be amazed, and laugh out loud as you read these posts, which I’ve indexed by the author’s first name. Don’t blame these authors for the dorky jokes in the cartoons, though. That’s all my fault. Aaron Bertrand is “looking back at bad interviews.
When you modify the indexes on a table, SQL Server needs to reconsider how it executes queries that reference that table. But the way this appears when you’re looking at your execution plan cache is far from obvious: Impacted query plans are NOT removed from cache at the time you change an index. The next time the query is executed, it will be recompiled, and the new plan and related execution information will be placed in cache.
Some of the biggest lessons I’ve learned about interviewing come from an interview experience that meant a ton to me – and all my dreams came crashing down.
A user recently asked me what a good use case might be to run SQL Server on Linux in a Docker container.
Welcome to T-SQL Tuesday for August 2017!
T-SQL Tuesday is a chance for you to join in the SQL Server community and write a blog post on a suggested topic. You can use this as a way to start a new blog, dust off a blog you haven’t used in a while, or make it part of regular blogging: your choice!
I would love for you to participate. The whole SQL Server community would. Please, join us!
One cool little feature in SQL Server 2016 is COMPRESS(). It’s a TSQL function available in all editions that shrinks down data using the GZIP algorithm (documentation).
Copyright (c) 2024, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.
