Announcing T-SQL Tuesday #87 – Fixing Old Problems with Shiny New Toys

Announcing T-SQL Tuesday #87 – Fixing Old Problems with Shiny New Toys

T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and I am thankful for the opportunity to host this month’s edition. The concept is straightforward – each month a blog hosts the party and everybody who wants to contribute can write a post about the topic that is selected.

I’ll get into a few more specific rules at the bottom of this post, but first let’s dive into this month’s topic!

This Month’s Topic: Fixing Old Problems with Shiny New Toys

While the SQL Server ecosystem is constantly evolving, it seems like that evolution has sped up considerably in the last year or two. From the constant improvements in Azure, to the rapid changes in Power BI, to the powerhouse release of SQL Server 2016 last year, those of us whose professional life resides within the SQL Server world have a multitude of new tools in our toolbox.

What I’d like to see from the blog responses for this T-SQL Tuesday is how you’ve used a “new” Microsoft data platform toy to fix an old problem. We’ll define new toys as something from SQL Server 2014’s release date until now. We’ll even accept a SQL Server vNext response if you’ve got one!

Did you work around a database design/performance issue by using memory-optimized tables and natively compiled stored procedures (brought to us in SQL 2014)? Did you use Power BI to present data visualizations to a client in a way you couldn’t have previously? Did you use SQL 2016’s mobile reporting ability to extend SSRS reports to a mobile client and solve an issue that way? Did you solve an archival issue by stretching your database into Azure? Basically, did you solve a data problem with a cool new Microsoft data platform toy?

I think many of us settle into old habits when it comes to solving problems with our data, so I can’t wait for the responses to this topic to see what cool new things people are doing to solve some old problems.

The Fine Print (aka The Rules)

  • Your post must be published between 00:00:00 UTC and 23:59:59 UTC on Tuesday, February 14th (yes, feel free to throw a Valentine’s joke or two into your blog)
  • Include the T-SQL Tuesday logo in the top of your post and link your post back to this one (preferably via a comment on this post, but a trackback is OK as well)
  • If you’re on Twitter, tweet your post using the #tsql2sday (if you’re not on Twitter, get on it!)

 

38 thoughts on “Announcing T-SQL Tuesday #87 – Fixing Old Problems with Shiny New Toys

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s