SQL Server

Microsoft SQL Server 2017 powers your entire data estate by supporting structured and unstructured data sources. It builds on previous versions of SQL Server, which have been industry leading for four years in a row and a leader in TPC-E. It scales to petabytes of data and allows customers to process big data through PolyBase using T-SQL over any data. SQL Server has also been the least vulnerable database during the last seven years. SQL Server 2017 brings data insights with business intelligence capabilities that provide analytics at a fraction of the cost on any device along with advanced analytics with support for R and Python.

More details about SQL Server are available in the SQL Server documentation.
If you have a technical issue, please open a post on the developer forums through Stack Overflow or MSDN.

Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add support for Row Pattern Recognition in T-SQL (SQL:2016 features R010 and R020)

    The ISO/IEC 9075:2016 standard (aka SQL:2016) introduces support for Row Pattern Recognition (RPR) in SQL. Similar to using regular expressions to identify patterns in a string, RPR allows you to use regular expressions to identify patterns in a sequence of rows.
    To me, it's the next step in the evolution of window functions. If you think that window functions are profound and useful, RPR is really going to bake your noodle.
    RPR has limitless practical applications, including identifying patterns in stock market activity, handling time series, fraud detection, material handling, shipping applications, DNA sequencing, gaps and islands, top N per…

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

    We’ll send you updates on this idea

    7 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support for standard nested window functions in T-SQL

    The ISO/IEC SQL:2016 standard defines a concept called nested window functions that allows you to nest two kinds of window functions as an argument of a window aggregate function. The idea is to allow you to interact with row markers representing strategic points in windowing elements like the beginning or end of the partition, beginning or end of the frame, the current outer row, and the current inner frame row.
    The two standard nested window functions are the nested row number function and the nested value_of expression at row function.
    The former allows you to refer in an argument of…

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

    We’ll send you updates on this idea

    5 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  3. Database Diagrams

    Please add Database Diagrams back in SQL SERVER Management Studio

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

    We’ll send you updates on this idea

    36 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Put Debugger back into SSMS 18

    The SSMS Debugger is critical for debugging complex T-SQL Queries, please return it to SSMS 18

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

    We’ll send you updates on this idea

    76 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  5. Optimise for Analytics configuration option

    Would love to have a new Server-Wide as well as the Database Scoped Configuration configuration that would be called "Optimise for Analytics" and that would server the purpose of tuning the Storage Engine & Query Processor specifically for the Analytical Workloads (Business Intelligence, Data Warehousing, Data Preparation for ML, etc).

    The actual functionalities to be controlled by this option would be such as: -E configuration, Query Optimiser huge preference for the Hash Joins, Bigger preference for the Batch Execution Mode for the Rowstore tables, Bigger preferences for the Scans and Prefetching for the Storage Engine, Bigger Columnstore Object Pool allocation…

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

    We’ll send you updates on this idea

    3 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  6. Run DBCC CHECKDB WITH PHYSICAL_ONLY automatically in the background

    When RAID controllers are idle, they automatically check the storage to make sure it's still okay. Why not SQL Server too?

    Some of the pieces are there – for example, SQL Server already has the ability to watch for idle CPU times and run Agent jobs when it’s bored. For starters, that’d probably be good enough to save a lot of small businesses from heartache. For the databases over, say, 100GB, it’d be really awesome to have resumable physical_only corruption checking – tracking which pages have been checked (just like how the differential bitmap tracks page changes), with page activity…

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

    We’ll send you updates on this idea

    16 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  7. Eager Index Spools Should Generate Missing Index Requests

    In query plans where an Eager Index Spool is directly after a data access operator, a missing index should be generated in the query plan, and/or missing index DMVs that describes the definition of the index needed to make the spool unnecessary.

    I would not expect this to happen when a Lazy Index Spool occurs above a subtree.

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

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow Updating Statistics on the Secondary Replicas of the Availability Groups

    Allow remote (on the secondary replicas) statistics update for the Availability Groups. Given that a lot of time the secondary replicas have extra resources
    Potentially this could lead into spreading & parallelising the statistics recalculation processes while doing maintenance or potentially even ad-hoc.
    The original idea behind this is described in the following blogpost – http://www.nikoport.com/2019/06/20/updating-statistics-on-secondary-replicas-of-the-availability-groups/

    22 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  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  9. Option to specify a location for the DBCC CHECKDB snapshot

    When you run DBCC CHECKDB, by default the snapshot is stored on the same drive as the database data file(s).

    It would be nice to be able to specify the location, if you have

    - Faster drives elsewhere
    - No space on the same hard drive
    - Less I/O traffic elsewhere

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

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support DISTINCT for STRING_AGG

    Currently STRING_AGG aggregates all strings passed as an input. It would be very useful to support DISTINCT, so it would concatenate unique strings only.

    Example:
    CREATE TABLE dbo.Test (a VARCHAR(255))
    INSERT INTO dbo.Test (a)
    VALUES('Str1')
    ,('Str2')
    ,('Str1')

    SELECT STRING_AGG(a, ',') FROM dbo.Test t

    It returns: 'Str1,Str2,Str1'

    SELECT STRING_AGG(DISTINCT a, ',') FROM dbo.Test t

    It would return: 'Str1,Str2'

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

    We’ll send you updates on this idea

    9 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  11. Parallelize Script Update Mode

    When moving SQL Server between Cumulative Updates, Script Update Mode runs against each database on the instance in series. This works fine on smaller instances, but with hundreds or even thousands of databases on an instance, this can add a lot of time (several hours) to the process of starting the instance for the first time with the new CU.

    Suggestion: Run Script Update Mode in parallel, up to the MAXDOP setting for the instance.

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

    We’ll send you updates on this idea

    3 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  12. Eager Index Spools Should Generate Wait Stats

    In query plans where an Eager Index Spool is directly after a data access operator, wait stats should be generated while the Spool is built. In a parallel plan, EXECSYNC waits are generated, but in a serial plan, you don't see anything. Problem scenarios will become more common when FROID is released and adopted.

    I would not expect this to happen when a Lazy Index Spool occurs above a subtree.

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

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  13. Database Level Option For Storing Wait Stats

    SQL Server 2016 introduced Query Store, and SQL Server 2017 CU3 brought us aggregated wait stats at the query level. This is great information for data driven DBAs who need to be able to track plan changes over time, etc.

    With that in mind, an additional data collector for wait stats per database would be a great product feature, independent from Query Store data collection.

    We all know the limitations of the wait stats DMVs now:

    - They're cumulative over time
    - They're instance-wide
    - There's a lot of potential noise from wait types that aren't registered

    If you wanna…

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

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  14. Porting SMO Library to .NET Core

    SQL Server has been ported to Linux for over a year now and it is time the complete SMO library (or what can be) is ported over to cross-platform as well.

    Only 9 or so core files have been ported over to .NET Core and this allowed the sqlserver module to port over a small set of cmdlets to PS Core. This does not work for other modules like dbatools that use a wider berth of the library.

    There are plenty of other modules in PowerShell (and applications too) that would like to provide cross-platform support for managing SQL Server…

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

    We’ll send you updates on this idea

    4 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  15. SQL Server vNext (post 2019) and NoSQL functionality

    Hello,

    This is an invitation for discussion to the SQL Server engine team and the community.

    IMHO, SQL Server vNext (post 2019) should beef up its NoSQL functionality.
    Specifically, its XML APIs.
    This area is dormant since 2005/2008 release.

    SQL Server currently supports the following:
    - a subset of XQuery 1.0, circa 2007
    - a subset of XPath 2.0, circa 2007
    - XSD 1.0 circa 2001

    The current w3c standards:
    - XQuery 3.1
    - XPath 3.1
    - XSD 1.1 circa 2012

    Everything is in place, even current support for the UTF-8 encoding in 2019.

    Famous Obamacare is implemented by using…

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

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  16. Dark Theme for SQL Server Management Studio 2017 (SSMS 2017)

    Dark Theme works well in Visual Studio and should be included in SSMS. It helps reduce eye strain after long periods of development and debugging.

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

    We’ll send you updates on this idea

    unplanned  ·  40 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  17. adomd core

    ADOMD.NET Client Needs .NET Core Support

    Please tell us when this will be available. We've been waiting years, and all ADOMD.NET does is XML over HTTP - it's pretty silly that there's no support for clients running on .NET Core!

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

    We’ll send you updates on this idea

    16 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  18. Make it possible to force plan in Query Store even if you are using table variable with Clustered index

    A Query containing a table variable with clustered index will not use the forced plan in Query store, because the name of the index will be different for every execution.

    Please make it possible to reuse the forced plan or possible to name the clustered index.

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

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  19. Populate object explorer when database is specified in connection

    If I make a connection with a specific database in the connectionstring as a database user (partially contained database) I am able to browse that database with the Object explorer. If I make the same connection through a database login this is not possible when the view all databases permission is not granted to this login. I would like the specified database to be browsable.

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

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  20. Explain why indexes were skipped

    Feature request: expose information about what indexes the optimizer considered while compiling an execution plan. Specifically, the index names and WHY the index was rejected for that particular query. This could potentially be included in per-operator execution plan properties (see attached mockup), an extended event target, or some other avenue.

    Reason: many developers and DBAs wonder why certain indexes on their tables aren't being chosen for specific queries. This gives them better tools to figure that out and make better use of the SQL Server product.

    I've blogged about this feature request in more detail here: http://joshthecoder.com/2018/06/21/feature-request-index-rejection-reasons.html

    This request was…

    148 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  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 195 196
  • Don't see your idea?

SQL Server

Feedback and Knowledge Base