I wouldn’t expect SSRS to get a whole lot more development. SQL Server Reporting Services strikes me as an NPC these days, with Power BI taking the new starring role. It’s been marked as “under review” for over 3 years, but I have a pretty bad feeling about this. #4: Add an SSRS ReportViewer for ASP.NET Core. Sometimes you really need to know the order when you’re processing a list. When you split a string with STRING_SPLIT, you get a table with the values, but they’re not guaranteed to be in order. #5: Add row position column to STRING_SPLIT. Instead, Microsoft just has to start fixing the problem by making databases more reliable. I get it – it’s not part of SQL Server’s defaults, it’s not a setup option, you have to learn about it to understand the risk, and Microsoft is never going to mount a user education campaign talking about how many corruption bugs SQL Server has. Despite the best efforts of the blogosphere, too many people just don’t check their databases for corruption. #6: Run CHECKDB automatically in the background. Going by the notes in the request, it sounds like MySQL does this, and so when people come over from MySQL, they’re surprised at how much harder this task is in SQL Server. Okay wait hold on, before you throw birds at the screen, they’re talking about how the world’s standards for XQuery, XPath, and XSDs have moved on since SQL Server first implemented those features. Azure Data Studio has this and I love it so much. #9: SSMS keyboard shortcut to execute the current statement. PostgreSQL and Oracle have the GREATEST/LEAST functions that work like COALESCE, allowing you to pass in a list of values and get the top or lowest. You’ve submitted thousands of bug reports and feature requests at, and here’s what you’ve voted as the top 10 requests right now: