Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Jason Squires

My feedback

  1. 107 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Automation » Bug  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Squires commented  · 

    Still happens now and for some reason it kicks off the job again if you are referencing an execution of a runbook. Also, reminder, Az.SQL 2.9.1 is the last one that works if you are using Get-AzSqlDatabaseImportExportStatus. Status fails after that for every version and mis-represents runbook success when the actual executed runbook is still running.

    Jason Squires supported this idea  · 
  2. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  (General Feedback) » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Jason Squires supported this idea  · 
    Jason Squires shared this idea  · 
  3. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jason Squires commented  · 

    Peter, I just did the same today. I renamed the sysadmin account back to sa and upgrade succeeded without an issue. This definitely needs to be fixed I would think. There is no reason why we should have to rename our already renamed sa account back to the original sa. Thanks for posting your results and solution as well!!!

    Jason Squires shared this idea  · 
  4. 39 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, thanx for the feedback.
    As Ben points out, if you know which fields on the Database object you need, you can use Server.SetDefaultInitFields to make sure the collection is initialized with all those fields in the first query.

    Is there a particular scenario, using the latest SMO NuGet, where use of SetDefaultInitFields isn’t sufficient to speed up the query noticeably?
    If you have an Intellitrace or XEvents trace I could use for reference it’d be a great help.

    Jason Squires supported this idea  · 

Feedback and Knowledge Base