What Do We Want to See in SQL Server?

  • I'd like to see:

    • LastLoginTime in sys.server_principals
    • ability in ssms to right-click on an object name in a query that will then select the object in the object explorer
    • index create time in sys.indexes
    • somewhere to add tags/metadata for databases and objects; like script references/descriptions/version#/owners

     

    these are probably very unlikely but would be useful:

    • a way to easily compare data between servers; like a checksum for the entire set of data for easy comparison
    • Basic AG without clustering
    • ability to restore single object from backup (sorry third-party tools)

     

     

  • https://feedback.azure.com/d365community/idea/1fa5cf18-5925-ec11-b6e6-000d3a4f0da0 - vote. I think last login time is great.

    Select in OE - SQL Search does this: https://www.red-gate.com/products/sql-development/sql-search/

    index time - https://feedback.azure.com/d365community/idea/9fec9e0e-3f25-ec11-b6e6-000d3a4f0da0

    Meta-data - extended properties do this

    Compare data - checksums have big problems and MS has left this to the ecosystem, like Redgate and others. I think this is likely something they will never build and you need to buy.

    Basic AGs - I don't know they'll remove the clustering requirement, but you don't need a cluster with shared storage if you're thinking of that.

    Single object restore - never will happen. It's not even worth it for most third parties, as it happens rarely. However, if you need it, then you need to pay for it.

    Disclosure, I work for Redgate

  • - Add wizard for PIVOT, like one in MS Access

    - Expand list of Boolean operators, add implication =>  and equivalence <=>. It is cumbersome and confusing writing NOT P OR Q instead P=>Q. For equivalence it is (NOT P OR Q ) AND (NOT Q OR P). Maybe people would use tem in CHECK constraints.

    Zidar's Theorem: The best code is no code at all...

  • Of course, if the SQL Server team actually implemented any of these suggestions, they would be making T-SQL even more proprietary. Maybe we should be directing to these requests to the ANSI SQL committee - if such a group exists at the moment.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • I want intellisense to work consistently.....

     

    And when there's a column overflow/truncation the error message should include the freaking column name.....

     

    BCP supporting database to database transfer so I don't have to do some janky dump to a temp file then import.

  • client tools are always tough.

    Column truncation has gotten better with 2019.

    bcp is unlikeley to go db to db, but it would be nice.

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply