Maybe more people would use the Central Management Server feature of Management Studio if it had a name that didn’t sound as utilitarian as a heat pump. Something like PowerServer. Or…Mega Instance Policy Ranger. Or…One Query To Rule Them All.
Because that’s what it really is.
As I’m sure you’re aware, the career path for a SQL Server DBA is a wonderful journey of growing your catalog of knowledge through unexpected lessons. For example: Did you find out the hard way you need to test restoring those backups? Did you discover you need to enable the dedicated admin connection after a server locked up? Did you learn the unexpected results of using reserved words as object names?
Don’t worry, you’re not alone.
Speaking of reserved words, I recently learned there’s a bit of a situation regarding a certain word and logical file names. Let me tell you a story.
Much like your paycheck, this post is two weeks after the fact. But also like your paycheck, it’s got a good deal of personal importance. I’ve taken a couple weeks to let the experience of attending my first PASS Summit marinate in my brain sauce, and now I’m ready to server up my thoughts.
You know what? Scratch that analogy. That’s a little too Hannibal Lecter.
So after fumbling the opening, here’s what I remember about PASS Summit.
Remember the Bill Gates email hoax? The one that claims to be some sort of Microsoft beta test saying Gates is going to pay cash money to anyone who forwards the email? I’m pretty sure it’s been around as long as actual email.
You knew that wasn’t real, right? It’s a myth. And speaking of perpetuated myths…
As I mentioned previously, this week I presented my first public SQL Server training session. I’m truly grateful for this opportunity because after all the work I put into preparing the session I believe I ended up with something that has value for just about anyone who writes T-SQL.
But for now, let’s have a few words about the words “all the work”.
As Sinatra was fond of singing, “regrets, I’ve had a few.” And one of those came this week immediately after my presentation. This isn’t to say the presentation didn’t go well – it did. At least I think it did. I had several people come up and thank me afterwards for showing them things they didn’t know previously, so in that sense it went well.
But in hindsight, one part of it, well, it sucked. So I’m going to take a moment here and now to correct that.
As noted in the previous post, this month I got my learn on at Tech Outbound’s SQL Cruise Alaska. Which was awesome in so many ways, but I’m only going to tell you about one. Because this one just might be of some value to you.
First a little background: Continue reading
Although I have experience with In-Memory OLTP on SQL Server, I don’t anticipate I’ll be writing about it much. If you want to learn about that subject I highly recommend checking out Ned Otter’s blog. Much like Marcel Marceau is to miming, Ned has quietly become the master of documenting In-Memory OLTP. So much so I’ve even heard Microsoft’s Bob Ward refer to Ned’s posts.
Meanwhile, since you’ve decided to stick around this site, let me share some bad news about the files supporting your In-Memory OLTP.
I’ve mentioned on this site that part of the reason I’m even writing my SQL Server notes here is because of my experience on Tech Outbound’s SQL Cruise Alaska last year. It was a more significant event for my career than I could have possibly imagined, and not just because of all the cool stuff I learned. I even found out I had something in common with Bob Ward.
But before I get to that, let me explain to you why I am investing in a second round for the 2018 Tech Outbound Alaska event next month.
In my previous post I discussed a particular query design that made the tempdb data files consume all available drive space. When discussing the resolution I noted one of the steps was to reduce the size of the data files. That’s means shrinking them, and I am fully aware that sometimes tempdb can stubbornly refuse to shrink. It’s kind of the reverse problem George Costanza mentioned about swimming.
So let’s talk about what you can do when tempdb requires shrinkage.