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.
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.