SQL Server security can mean different things to different people. And rightly so. The first thing I always think of is authorization. And that is why I'm stepping onto my soapbox, blogging my frustration into the ether. I see four recurring security blunders that drive me nuts. The blundees (is that a word?) are seemingly oblivious. They react as if everything is fine and anyone that suggests otherwise is unreasonable. Allow me to immortalize their folly, National Memorial-style.
I've been taking a few steps down a path that's new for me. So keep that in mind if you've been down this path too. Because you've likely traveled farther than me and the lens you look through offers more clarity than mine.
I'm a long time Celtics fan living in Florida, so I don't normally get to see them play much during the regular season. I'm relegated to the occasional matchups vs Orlando (my cable provider shows all the Magic games), plus any other games televised nationally on ESPN, NBA TV, or TNT. The rest of you vagabond fans probably face the same challenge. For the 2016-2017 NBA season, I subscribed to NBA League Pass for the first time. It hasn't been pretty.
Today's less-than-ugent challenge was to un-pivot the output of RESTORE HEADERONLY. I thought for certain someone else, somewhere, at at some time must have wanted to do the same thing. So I asked the Twitterverse, but no one responded. I guess I'll have to make do myself without the easy button. No worries, though. We can do this!
I ran into a SQL Server connectivity issue this week that was a puzzler, but (thankfully) only for a short time. Maybe my pain can be your gain. Here's a quick rundown.
I installed and configured a new instance of SQL Server. After getting appropriate firewall ports opened by the network team, everything seemed A-OK. Until I tried connecting from a remote machine. Here is what I saw from SSMS:
Thomas LaRock wrote a blog post a couple of months ago that really irritated me. It was about the future of the DBA. My first instinct was to write a rebuttal blog post of my own. In my mind I would "throw the bullshit flag" and remind everyone that speculation is an exercise in futility. I'd insist that until his predictions start happening, he's just guessing and full of crap. Let's just say that blog post, if written, would have quickly been added to the list of really dumb things I've done in my lifetime.
I experienced a handful of "firsts" this month. I installed Windows 10, followed soon after by installing SQL Server 2016 and SSMS 2016. It didn't take long for me to hit the CTRL+F keyboard shortcut in SSMS, which of course opens the "Find" dialogue. In the particular version of the Visual Studio Shell that SSMS is built upon, the Find dialogue is quite different than in previous of the shell. But this wasn't a shock to me. I'd seen in before in other Microsoft products including Visual Studio Express and Visual Studio Community.
Restoring a backup of [master] from one instance to another is challenging. The source and target instances have to be the same version. And after [master] is restored, the instance won't start if it can't find the files for [model] or the path for [tempdb] files. Those are just a few concerns that I can think of off the top of my head. Here's another one I've added to my list: encryption. No, I'm not using TDE, but I am using native backup encryption.
On this date 27 years ago, the Boston Celtics came to Orlando for the first time--well, it was the first time they played against the Orlando Magic on the road. I was a very tiny part of that history. Way back in January of 1990, I was just starting the Spring semester of my third year at UCF. Monday the 15th was Martin Luther King Day, and there were no classes that day.
If you've seen some of my recent posts, you know that Extended Events have been on my radar. So let's look at some Connect items for XEvents.