Twenty Snazzy Bloggers!
There’s always some anxiety when throwing a party. Wondering whether it will be a smash. Well I had nothing to worry about with the twenty bloggers who participated last week. You guys hit it out of the park!
The Round Up
Let’s get to it:
Rob digs into the query optimizer to highlight an interesting plan choice when temporal tables are involved. So extra care is needed when indexing and testing features that use temporal tables.
What I Thought: I really enjoy Rob’s posts that digs into query plans and the optimizer in general.
Did you know that Rob has participated in every single T-SQL Tuesday? Even the rotten months when there’s like only three participants. Rob’s one of them.
Ginger writes about how to get started coding with the R language.
What I Thought: If you want to do the kind of analysis that R enables then bookmark her website! Her blog is becoming a real resource when it comes to working with R and SQL Server.
Have you ever had to troubleshoot spinlock bottlenecks? You have my sympathies. Spinlocks are meant to be internal to SQL Server, something that Microsoft worries about. Ewald writes about new SOS_RWLOCK improvements.
What I Thought: Do you like talks by Bob Ward? Do you like to dig into SQL Server’s internals? Does inspecting SQL Server debuggers and callstacks sound like a fun evening? This post is for you.
Russ hasn’t posted to his blog recently because he’s been busy creating In-Memory OLTP courseware. So I’m glad that Russ is taking a break from that, returning to blogging and writing about … In-Memory OLTP. Specifically
What I Thought: I like Russ’s style. He has to keep things professional and respectable for Pluralsight, but on his own blog he gets to talk about sandwiches, ulcers and tempdb.
To be clear, Guy talks about why the wait-for-sp1 advice doesn’t apply.
What I Thought: One sentence Guy wrote struck a chord with me: “I have never agreed with this claim, but in my first years as a DBA I didn’t have enough experience and confidence to claim otherwise, so I just assumed those people know what they’re talking about.” Wow, I’ve recognize that feeling. All I can say is that when you get past that feeling. That’s a really really good sign.
Patrick gives a recap on a SQL Server hackathon called “SQL Server 2016 Launch Discovery Day”.
What I Thought: Wow, read the whole post, but if you can’t, at least check out the challenges and the scoring criteria. For example, the first challenge is to answer “From how far away do attendees travel to SQL Saturday? Are there any geographic trends to the distances traveled”. How would you approach this?”
Justin describes query regressions he found in benchmark workloads when run against SQL Server 2014 and SQL Server 2016. Then, in 2016, he shows how to use Query Store to fix it!
What I Thought: Fantastic post. And probably the best organized post of the month.
My friend Ken introduces the SSMS feature of comparing query plans.
What I Thought: I have to admit that after reading his post I tried the feature out last Tuesday. I’ve since found myself using the feature a few times since. It’s a valuable tool for database developers. Thanks Ken!
Andy wrote about new functions COMPRESS and DECOMPRESS which do that using the gzip algorithm. Andy gives an example of how you would use COMPRESS and what situations would make best use of this feature.
What I Thought: I did not know about this. It’s a feature that I will use (once we adopt 2016).
Erik introduces direct seeding for Availability Groups. Direct seeding lets DBAs avoid a step when launching a new replica.
What I Thought: Apparently if you’re a DBA this is a CoolThing™. I kind of lost my taste for replication solutions – specifically transactional replication on flaky networks – in 2004. It’s nice to see that eleven years later, Microsoft is still working on making it easier to “move data from here to there”. (On the sincerity-sarcasm meter, that lies somewhere in the middle)
Temporal tables – not to be confused with temp tables – are the subject of Deb’s post. Earlier Rob Farley warned us to be careful about indexes on temporal tables. In Deb’s post, we’re warned about the precision of datetime2 columns in temporal tables.
What I Thought: Thanks for writing Deb, I like your perspective and how you walk us through your thinking. Very compelling.
Chrissy Lemaire, Powershell MVP writes about how it’s still hard to migrate logins using only SQL Server. However there’s an easy solution using powershell.
What I Thought: Chrissy is one of the bloggers who used my “It’s 2016, why is X still a thing?” writing prompt. Chrissy also points out how rapidly powershell is growing to better support DBAs. It turns into a very exciting story.
Fellow Canadian and all around good guy Aaron also used the “It’s 2016, why is X still (not) a thing?” format. As developers, we’d like a way to use Developer edition to be able to deploy to Standard edition confidently without worry that we’ve accidentally used some feature only available in Enterprise Edition.
What I Thought: Aaron’s absolutely right and I’ve been burned by this missing feature in the past. He links to two connect items and asks us to vote on them and leave business impact comments. I encourage you to do that too.
Robert writes about SQL Server 2016 launch activities and three features he’s excited about, temporal tables, query store and better default tempdb configuration.
What I Thought: It appears that NYC was the place to be when SQL Server 2016 launched. Maybe I’ll keep my calendar clear for SQL Server 2018.
Row Level Security is Steve’s topic. He describes what it is, how it’s used and how he’ll never have to implement that feature from scratch again.
What I Thought: Steve is optimistic about the feature and I am too. I think I was first introduced (in a way) to the idea behind the feature when I tried to look at sys.procedure definitions as a data reader.
Lori’s writes a good introduction to temporal tables.
What I Thought: You know how when you visit documentation on a SQL Server keyword or function, you have to scroll to the bottom of the page to see an example? Not so with Lori’s introduction, her examples are up front and excellent.
Mike Fal is the second one to mention direct seeding for Availability Groups. Nice! This promises to be a good feature for DBAs.
What I Thought: In Erik’s post, he mentioned the lack of SSMS support. And so he pointed to a connect item about it. Mike Fal recognizing the issue tackled it with powershell. Good job.
New JSON support! I was glad that someone wrote about it. And Taiob’s not just a JSON user. His workplace uses MongoDB as well.
What I Thought: Thanks Taiob, At first I noticed your website’s domain: “SQLWorldWide” and wondered if you chose that name based on Microsoft’s new sample database World Wide Importers, but then I noticed you’ve been blogging for a while. If you know SQL Server and want to know what JSON is all about, this post is for you. If you’re a developer who uses JSON and want to know how to incorporate it into a SQL Server solution, this post is for you too.
Kennie writes about temporal tables. Wow, this seems to be a popular feature this year. He explains how relevant this feature is when compared with more traditional ways to implement type 2 history tables (slowly changing dimensions).
What I Thought: Kennie mentions watching Chris Date and warehouse scenarios, so it’s nice to have the perspective of someone familiar with relational theory and also with data warehouses.
Thanks again everyone. Have a wonderful summer and a wonderful 2016!