Jason Squires

My feedback

  1. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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  · 
  2. 39 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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