Ben Miller

My feedback

  1. 20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller commented  · 

    This is very disruptive when you have a lot of time invested into managing statistics and have samples persisted. There is an option to keep NORECOMPUTE on or off, but nothing for the PERSIST_SAMPLE_PERCENT. It just takes it away.
    Please don't leave us to roll some extravagant solution. Fix this issue.

    Ben Miller supported this idea  · 
  2. 8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller commented  · 

    Any updates on this one Matteo?

  3. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  4. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  5. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  6. 25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller commented  · 

    This is making things really difficult in the DevOps place. With this resetting things right now, we have to exclude sequences and then put code in the Pre-Deployment to detect whether or not the SEQUENCE exists and if not then create it. If you don't exclude sequences then you have to put code in the post deployment script to update the restart with for the max value of the table.

    Ben Miller supported this idea  · 
  7. 236 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 » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 72

    <=-=Mar 10 2016 11:26AM=-=>

    It’s a shame that this was submitted as just a “suggestion”. It should actually be listed as a “bug” because there’s only a comparatively small set of use cases where enumeration of the result set of elements is not important.

    <=-=Mar 11 2016 12:47PM=-=>

    I agree that an order column is required; one example use case is where two lists are passed in, and ordinal positions in one list correspond to positions in the other.

    <=-=Mar 11 2016 3:12PM=-=>

    Please see the related suggestion: STRING_SPLIT needs “RemoveEmptyEntries” option, like String.Split in .NET ( https://connect.microsoft.com/SQLServer/feedback/details/2462002/ ).

    <=-=Mar 12 2016 12:02PM=-=>

    This kind of function is primarily needed for de-serializing previously serialized arrays of values of any type format-able as text.
    I therefore recommend to have the result set of this function work excellent with this use-case.

    With de-serialized arrays there is a need to…

    Ben Miller supported this idea  · 
  8. 40 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 » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  9. 22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  10. 30 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  12 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  11. 105 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  12. 37 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.

    Ben Miller commented  · 

    all you have to do is to have 300 databases and get a Server object whether by new-object or by importing SQLServer module. Then using this:

    $server.Databases.ID and sit and wait and wait.

    But these IDs are in sys.databases. If you look at the query that is issued behind the scenes includes mirroring and many other things that really do not relate and may never be interrogated.

    I will let Chrissy illustrate her take on the enumeration she is talking about.

    Ben Miller commented  · 

    Yes, this is due to the silly query that comes from a Database object where the only default init field is Name. Whenever any other property is accessed (without employing Server.SetDefaultInitFields) it produces a very bad query that takes a while to execute and with 100's of databases or more, it is deadly.

    Ben Miller supported this idea  · 
  13. 293 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
  14. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller commented  · 

    If I am scripting out the Server Login, it should have high fidelity as the login that was created.

    I am not sure what the security reasons there would be with the password as it is hashed one way anyway, so give me the real password. If I have permissions to script it out, this could be important for migrations.

    Ben Miller supported this idea  · 
  15. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Miller supported this idea  · 
    Ben Miller commented  · 

    This seems to be a common problem that force us to update the statistics in the system tables.
    Using this you should be able to get this resolved. This does not keep from calling this a problem when upgrading databases. This maybe should happen when you upgrade your databases as part of the upgrade on the system side.

    update statistics sys.[sysclsobjs] with fullscan
    update statistics sys.[syscolpars] with fullscan
    update statistics sys.[sysidxstats] with fullscan
    update statistics sys.[sysiscols] with fullscan
    update statistics sys.[sysobjvalues] with fullscan

Feedback and Knowledge Base