SQL Server

Microsoft SQL Server 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 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.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Trace Flag/sp_configure Option to Allow Developer or Evaluation Editions to "Act" like Standard Edition

    One of the challenges for many customers who need to use Standard Edition is that both Developer and Evaluation Editions of SQL Server are the same functionally as Enterprise Edition. This means that in non-production scenarios/environments, without buying a full license of Standard Edition (or having MSDN), you are potentially using (or able to use) features not available in Standard. Dev and Eval should have a way to allow those who will ultimately be using Standard to constrain what features are used as well as any performance limitations in Standard so their eval/dev/testing efforts are accurate.

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

    We’ll send you updates on this idea

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

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

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

    We’ll send you updates on this idea

    under review  ·  307 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

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

    We’ll send you updates on this idea

    under review  ·  9 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Restore a table from a backup

    Hi Msft team!
    I'm writing to reccomending a new feature that will help us a lot! Every time that we have data issues (truncate or DML by accident) we need to restore the entire database or filegroup and that takes a lot of time! it will be awesome if you can add the posibility to restore a table from a backup or restore to a point in time directly from SSMS instead off the whole process.
    I hope this helps!
    Thank you!

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

    We’ll send you updates on this idea

    98 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  5. SSMS 15.0.18330.0 import bacpac failed

    With the latest SSMS 15.0.18330.0 I'm unable to restore an Azure SQL Bacpac, error is triggered when "Importing datase".

    If I try to get more details (clicking on the "Error" link), I get an NRE :

    TITLE: Microsoft SQL Server Management Studio

    Object reference not set to an instance of an object. (Microsoft.Data.Tools.Schema.Sql)

    at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeploymentPlanGenerator.DeploymentScriptDomGenerator.GenerateFragment(Int32 operation, IModelElement element)
    at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeploymentPlanGenerator.DeploymentScriptDomGenerator.GenerateSteps(Int32 operation, IModelElement element)
    at Microsoft.Data.Tools.Schema.Sql.Deployment.OrderedStepGenerator.Add(DeploymentScriptDomGenerator scriptDom, IModelElement element, Int32 operation)
    at Microsoft.Data.Tools.Schema.Sql.Deployment.Analyzers.PlanMediator.BuildDependencyOrderedSteps(Int32 operation, List1 classOrder, List1 operationOrder, Dictionary2 changes, Boolean preserveGraphs, Dictionary2& relating, Dictionary2& related)
    at Microsoft.Data.Tools.Schema.Sql.Deployment.Analyzers.PlanMediator.BuildOperations()
    at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeploymentPlanGenerator.OnGeneratePlan()
    at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeploymentPlanGenerator.GeneratePlan(List
    1 drops)
    at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeployment.BuildPlan() …

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

    We’ll send you updates on this idea

    7 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Matteo Taveggia responded

    Thanks for reporting this issue. I may have to reach out to the DacFx Team.

    Would you be able to share the bacpac with us, perhaps on OneDrive or equivalent? I do understand that it may contain sensitive information and may not be an option for you.

    Thanks,
    -Matteo

  6. 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/

    60 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 →
  7. Unable to deploy SSIS packages from Visual Studio 2017 (15.8.0)

    The latest version of Visual Studio 2017 (15.8.0) appears to have introduced a bug preventing deployment of SSIS project files.

    When attempting to connect to a server the deployment wizard returns the following error:

    TITLE: SQL Server Integration Services

    Could not load file or assembly 'Microsoft.SqlServer.Management.IntegrationServicesEnum, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)


    ADDITIONAL INFORMATION:

    The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)


    BUTTONS:

    OK

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

    We’ll send you updates on this idea

    under review  ·  93 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…

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

    We’ll send you updates on this idea

    21 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ambiguity on OLE DB Driver 18 for SQL Server download page

    The "Microsoft® OLE DB Driver 18 for SQL Server®" download page allows you to download two identically named files with no disambiguation. Obviously, one is for 32bit and one is for 64bit, but the page provides no way to tell which one.
    Problem is on download site here: https://www.microsoft.com/en-us/download/details.aspx?id=56730
    Can we get some identifying information associated here when choosing which of the files to download? Confusing to have no way to tell which one is 64bit.

    1 vote
    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 →
  10. develop a SSRS ReportViewer for ASP.NET Core

    Develop a SSRS ReportViewer for ASP.NET Core

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

    We’ll send you updates on this idea

    under review  ·  144 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  11. ssms query store issues/suggestions

    SSMS 18.4

    Bugs


    1. When using the detailed grid (with additional details) returning 'Top nn', it is not returning the same metrics that is shown in the simple grid and chart. It does work correctly when returning 'All'. Test case: the same set of query id's should be listed in all cases.

    2. Sorting by a column in the simple grid, it changes the metric which does not match the configured metric. This works correctly in the detailed grid. Test case: the same set of query id's should be listed in all cases.

    3. Sorting by a column should not query the Query…
    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Ack on the reported issues under the Bugs section. Thank you for reporting.

    For future reference, it would be more actionable if what’s under Annoyances and Suggestions could be opened as separate feedback items (maybe even if collating those that may be related), but let them accrue votes from other community members on those separate scoped items.

  12. Add SSIS to the SQL Server Docker Image

    I work for a large bank which it trying to move hundreds of SSIS packages into GitLab pipelines. This task would happen faster an easier with SSIS on the MS SQL Server Docker image.

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

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  Setup + Deployment  ·  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 figure out what's…

    290 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. SSMS 18.0 unable to export Extended Events XEL to XEL

    SSMS 18.0 is unable to export an Extended Events XEL file to another XEL file.

    When viewing an XEL file in SSMS, using the Extended Events menu command "Export to" > "XEL file..." results in this error:

    (Error Summary)

    TITLE: Microsoft SQL Server Management Studio

    Method not found: 'Void System.Object.SerializeEvent(Microsoft.SqlServer.XEvent.Linq.IEventSerializer, Microsoft.SqlServer.XEvent.IMetadataGeneration)'. (Microsoft.SqlServer.XEvent.Linq)

    BUTTONS:

    OK

    (Error Detail)

    Method not found: 'Void System.Object.SerializeEvent(Microsoft.SqlServer.XEvent.Linq.IEventSerializer, Microsoft.SqlServer.XEvent.IMetadataGeneration)'. (Microsoft.SqlServer.XEvent.Linq)

    Program Location:
    at Microsoft.SqlServer.XEvent.Linq.XEventFileProvider`1.SerializeEvent(IEventSerializer serializationContext, TEvent serializableEvent)
    at Microsoft.SqlServer.XEventStorage.ComputedGridStorage.SaveData(Object param)

    I reported this same issue for a previous version of SSMS (17.?) via connect item 3136373 on 2017-06-22 and it was fixed in a later minor update…

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

    We’ll send you updates on this idea

    6 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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…

    175 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 →
  16. URGENT: "Feature Restrictions" actually increases chances of SQL Injection and must be removed immediately (before RTM)

    The new "Feature Restrictions" feature that was introduced in CTP 3.2 of SQL Server 2019 is highly problematic. It is an ill-conceived feature that does not prevent SQL Injection in any way. It doesn't mask user error messages (only system errors), and it prevents WAITFOR but not a WHILE loop that accomplishes the same delay. So this feature is absolutely useless.

    Actually, it's worse than that because people will assume that this feature actually does prevent these things, which will give them a false sense of security.

    This feature is not fixable and needs to be removed entirely. This needs…

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

    We’ll send you updates on this idea

    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Recursive CTE breaks SQL Server service

    Query below crashes SQL Server service. Tested on SQL Server 2017 Developer Edition CU16.

    ;with cterecursive as
    (
    select
    convert(char(8000), '') column1
    ,convert(char(79), '') column2
    union all
    select
    convert(char(8000), '') column1
    ,convert(char(79), '') column2
    from cte
    recursive
    )

    select *
    from cte_recursive

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

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. SSDT for Visual Studio 2017 - Include as part of the VS 2017 Installer

    Can we please pass over the SSDT components to the Visual Studio team so this can be included as part of the Visual Studio 2017 installation process?

    The VS team can then build out the installer in a way that SSDT is always compatible with their latest build and installer. We've been stuck with the break fix break fix loop with SSDT and incompatibility with VS upgrades for too long now. The SSDT team doesn't respond quickly enough, the latest example being SSDT 15.6/VS 2017 15.7.x installation issue, why are we waiting so long for an installer update?

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

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  19. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Restore multiple instance support for Reporting services in SQL 2017

    Please restore the multiple instance support per server for Reporting Services 2017. SQL Server reporting Services has supported multiple instances on one server in versions SQL 2000 thru 2016 and it was removed by design with the release of SQL 2017. This was a bad move as it will force my company to deploy 6X as many servers to deploy what is a lightweight application server.

    I'm not sure if this has anything to do with the PowerBI integration with SSRS, but it also suffers from this bad decision as well.

    Best Regards,
    James Fuller
    James.fuller@amwins.com

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

    We’ll send you updates on this idea

    under review  ·  46 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 232 233
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base