WE DID IT! Microsoft Fixed Those 3 SQLPS Issues in SQL Server 2016

Apr 3, 2016 · 2 min read  ·
Share on:

In my previous blog post "Can We Get These 3 SQLPS Issues Fixed before SQL Server 2016 RTMs?", Aaron Nelson and I asked the SQL and PowerShell community to help upvote 3 SQL Connect items. The items addressed three problems with SQL Server's PowerShell module, SQLPS.

  • It took 3-5 seconds to load
  • It changed the present working directory when loaded
  • It produced approved verb warnings when loaded

Today, Microsoft responded, letting everyone know that the issues were addressed in SQL Server Management Studio March 2016 Refresh.

@cl fixed in #SSMS March 2016 Refresh. https://t.co/Jn4saqosIt

— Ken Van Hyning (@sqltoolsguy) April 2, 2016

That is absolutely amazing! Your 243 combined upvotes helped this happen:

sqlps

Check that out! Fixed verbs + backwards compatibility. No changing of the present working directory. And SQLPS now loads in 0.22 seconds instead of 5 seconds.

But wait, there's more!

Microsoft's "SQL Tools Guy" Ken Van Hyning left the following comment in the previous post:

 Please keep the connect bugs and suggestions coming. We are working on making more improvements to SQLPS in the months ahead. 

You saw that right! Microsoft is working on SQLPS! And they want to know what needs fixing.

Let Them Know What's Broken in SQLPS

The best way to let the SQL Server Team know what you'd like addressed is by using SQL Server's Connect Feedback page. To file a bug or suggestion, click the link, then search to see if your bug has already been submitted. If not, click the Submit feedback button, and fill it out.

mahbug

We found that effective bug and suggestion reports include the following if at all possible

  • Why the issue matters
    • "Slow load times decrease adoption rates"
  • A solution if at all possible
    • "Remove line 7 and replace with XYZ because it is a more efficient call"
  • Address potential concerns
    • "Backwards compatibility can be addressed by using aliases for the unapproved verbs."

Of course, this is just a suggestion. It's what worked well for us. Oh, and if you haven't already, please upvote the request for Microsoft to Open Source SQLPS by putting it on GitHub, and publishing it to the PowerShell Gallery.

And finally, thank you to everyone Microsoft that helped make this happen!