2017 – Page 2 – T-SQL Tuesday

2017 T-SQL Tuesdays

December – T-SQL Tuesday #97 – Setting Learning Goals for 2018

November – T-SQL Tuesday #96 – Folks Who Have Made a Difference

October – T-SQL Tuesday #95 –Big Data

September – T-SQL Tuesday #94 – Let’s All Get PoSh

August – T-SQL Tuesday #93 – Interviewing Patterns and Anti-patterns

July – T-SQL Tuesday #92 – Lessons learned the hard way

June – T-SQL Tuesday #91 – Databases and DevOps

May – T-SQL Tuesday #90 – Shipping Database Changes

April – T-SQL Tuesday #89 –The times they are a-changing

March – T-SQL Tuesday #88 – The Daily (database-related) WTF

February – T-SQL Tuesday #87 –Fixing Old Problems with Shiny New Toys (roundup)

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!

January – T-SQL Tuesday #86 – SQL Server Bugs and Enhancement Requests (roundup)

Find the most interesting bug or enhancement request (and it can be your own), and write a blog post about it

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

Invitation and roundup from Matt Gordon.

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.

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.

T-SQL Tuesday #86 – SQL Server Bugs and Enhancement

Invitation and roundup from Brent Ozar.

I know this is going to come as a stunning shock to you, dear reader, so you may want to be sitting down.

SQL Server isn’t perfect.

It’s okay. Deep, calming breaths. We’re going to get through this together, and here’s how:

Go to Connect.Microsoft.com, the place where we file bug reports and enhancement requests
Use the Search to search for your favorite commands, or keywords like error or incorrect results
Realize that the search function is incredibad, and instead switch to using Google to search for terms or bugs marked as won’t fix
Find the most interesting bug or enhancement request (and it can be your own), and write a blog post about it (including a link to the Connect item so that folks who agree with you can upvote the item)

The Connect item doesn’t have to have anything to do with T-SQL – it could be about the engine, SSRS, R, the installer, whatever. Now, more than ever, Microsoft has started to respond to Connect requests and get ’em fixed not just in upcoming versions of SQL Server, but even in cumulative updates for existing versions.

It’s an incredible rush of a feeling when you see that Microsoft closes one of your favorite bugs as fixed. It’s happening fast these days – and I want you to enjoy that feeling too. So it’s time to get to know Connect!