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. SSMS:Add a Keyboard Shortcut that Executes the Statement where the Cursor is placed

    Having to select statements by clicking and holding the mouse is just bad ergonomics. Request to have a keyboard shortcut which runs the current sql statement. The current sql statement is defined based on where the cursor is placed. For example, proposed shortcut runs only runs a single sql statement to the next semicolon. This shortcut would be an equivalent to Oracle's SQL developer's ctrl + enter shortcut. Note that this is probably the most used shortcut in SQL Developer and not having an equivalent on SQL Server Management Studio is disappointing. I know that not everyone ends their statements…

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

    We’ll send you updates on this idea

    18 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add AAD Auth to Invoke-SqlCmd

    Please add Azure Active Directory authentication as an option for the Invoke-SqlCmd cmdlet to connect to an Azure SQL DB.

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

    We’ll send you updates on this idea

    11 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  3. SEQUENCE gets reset on Publish from SSDT DB Project

    When you add a sequence to a database project and have it start at 1 and then deploy the project to a database, the first time it gets created correctly.
    When you get more values and the sequence next value is 100 and then publish the project again, the publish generates an ALTER SEQUENCE dbo.SequencObject RESTART WITH 1; statement and that should not happen when the sequence object already exists.

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

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. Performance Dashboard / Expensive Queries / copy query text

    When using the reports in the SSMS Performance Dashboard, you are unable to copy the query text from any of the "expensive queries" reports. Make it so you can either click to view the query in a new query window, or right-click the query to copy the text for pasting into a new window.

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Database diagram kills SSMS

    When i want to open an existing diagram in SSMS 18.2 on a database which is on compativity level 100 SSMS closes and restarts immediately. I also tried it with a new diagram - this seems to work.

    13 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 →
  6. Remove Brackets from SSMS script generation

    I won�t argue technical merits and I doubt this will sway the 800 lb. gorilla. But all one need do is listen to the chatter on the internet to realize that the use of brackets in SSMS script generation is a royal PIA. I respectfully request an option to remove them in SSMS. At the end of the day, you know this can be done and it would make a whole lot of of MSFT customers happy. Thank you.

    12 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 →
  7. SSMS 17.3 excessive memory usage

    SSMS consumes large amounts of memory & CPU, even when idle. Disabling intellisense has no effect

    12 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 →
  8. Registered Server modifications via SQLServer PowerShell module bug

    There is an apparent bug in version 21.1.18068 of the SQLServer PowerShell module when creating Registered Servers groups and registrations. When created at the PowerShell prompt they are not reflected in the Registered Servers window (even after refresh, or reboot). Existing groups and registrations seen in the Registered Servers window are not available at the Powershell prompt using commands such as dir or Get-ChildItem.

    The commands I use to create groups and registrations at the PoweShell prompt are similar to:

    group

    New-Item -Path "sqlserver:\SQLRegistration\Database Engine Server Group\AllServers"

    registration

    New-Item -Name $(encode-sqlname 'sqlsrv') -path "sqlserver:\SQLRegistration\Database Engine Server Group\AllServers" -ItemType Registration -Value…

    6 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 →
    planned  ·  Matteo Taveggia responded

    Thanks for the suggestion. We are going to take a look and get back to you.

  9. Set the Maximum Size of the SQL Server Error Logs

    In SQL Server 2012 and later versions, you can use xpinstanceregwrite to set the maximum size of individual error logs. Please make this setting available via SMO, instead of having to use xpinstanceregwrite.

    Documentation for this feature can be found here: https://support.microsoft.com/en-us/help/2199578/how-to-manage-the-sql-server-error-log

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

    We’ll send you updates on this idea

    1 comment  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Error in SSMS 18.5 setting baselines in Vulnerability Assessment

    When running Vulnerability Assessments in SSMS 18.5, then trying to set a result as baseline, we receive the following error. This occurs on multiple machines against a SQL 2016 database. It works correctly in SSMS 17.9

    TITLE: Microsoft SQL Server Management Studio

    VA1095 - Failed to set baseline. (Microsoft.SqlServer.Management.ThreatDetection)


    ADDITIONAL INFORMATION:

    One or more errors occurred. (mscorlib)


    Could not load file or assembly 'Microsoft.Azure.Storage.Common, Version=11.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (DataSec.VA.Core.Baseline)


    BUTTONS:

    OK

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

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  11. SQL Server 2019 Master Data Service: Number editing fails

    Upgraded SQL 2017 MDS to SQL 2019 RTM. Editing an decimal value of an entity fails when regional language is set to german. Can't use "," as an decimal seperator, When language set to an english then editing works fine when using "." as decimal seperator

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

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. SSMS: Allow forcing case-insensitive matching in Object Explorer filters

    In SSMS, when filtering objects in Object Explorer, comparisons on string properties (e.g. Name) use the collation of the database or instance, depending on whether you are filtering database-level or instance-level meta-data, respectively. Hence, when either level is using either a case-sensitive or binary collation, it is not possible to do a case-insensitive search of objects at that level. Having a "case-insensitive" check-box per each filterable Property would be super awesome 😺. Even better might be a "flip case sensitivity" check-box that would then also make it a case-sensitive comparison in an otherwise case-insensitive context.

    This situation lead to the…

    5 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 →
    planned  ·  Matteo Taveggia responded

    Thanks for filing this request. We’ll take a look at it and prioritize.

  13. SSMS: Object Explorer Filtering allows for SQL Injection (oops)

    When applying filters in Object Explorer (in any "Filter Settings" dialog) in SSMS 17.9.1 and 2018 Preview 6 (and possibly versions prior to 17), it is possible to inject SQL into the query executed by SSMS, simply by using a single quote / apostrophe. Yes, the app code clearly escapes a single apostrophe into two apostrophes, but the string containing the apostrophe is concatenated into a Dynamic SQL string executed via sp_executesql. The string entered via the UI to filter on is intended to be used within a string literal within the Dynamic SQL string. In this case I filtered…

    5 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 →
  14. SSMS Removes comments when Enable Parameterization for Always Encrypted checked

    When you have Both of these settings


    1. In the Connection Properties of the Connect to Database Engine, go to Additional Connection Parameters and enter the following: Column Encryption Setting=Enabled


    2. Right click on your query pane and to go Query Options => Advanced => select Enable Parameterization for Always Encrypted


    Now try to alter a proc that has comments in it

    Viola. Comments are gone and all lines have been reformatted to put a SQL Command into a single line.

    4 votes
    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 →
  15. SSMS 18 opens wrong server log

    SSMS 18.0 always opens the current server log even if you've double-clicked an older archive log in the object explorer.

    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 →
    planned  ·  Matteo Taveggia responded

    Thanks for the reporting the issue. We’ll take a look at it and prioritize accordingly.

  16. PowerShell get-item for SSIS package returns "number of keys" error

    PS SQLSERVER:\SSIS\VDEMO\DEMO\Catalogs\SSISDB\Folders\Demo\Projects\Deployment\Packages> $pkg = get-item 'Package.dtsx'
    Get-Item : Cannot retrieve the dynamic parameters for the cmdlet. SQL Server PowerShell provider error: The number of keys specified does not match the number of keys required to address this object. The number of keys required
    are: Name.
    At line:1 char:8
    + $pkg = get-item 'Package.dtsx'
    + ~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidArgument: (:) [Get-Item], ParameterBindingException
    
    + FullyQualifiedErrorId : GetDynamicParametersException,Microsoft.PowerShell.Commands.GetItemCommand

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

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. SSMS 17.3 IntelliSense does not recognize CATALOG_DEFAULT as a valid collation

    Management Studio, with IntelliSense enabled, does not seem to know that "CATALOG_DEFAULT" is a valid collation option. The name is underlined in red with a tool tip of:

    Invalid Collation 'CATALOG_DEFAULT'.

    Yet, it clearly is not invalid since it does work :-).

    I have observed this behavior in SSMS 17.1 and now in 17.3.

    I have tested with both SQL Server 2012 and 2016.

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

    We’ll send you updates on this idea

    8 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Matteo Taveggia responded

    Thanks for the reporting the issue. We’ll take a look at it and prioritize accordingly.

  18. SSMS v18.5.1 Object error when using Import Flat File

    When importing a file via the Import Flat File an Object Error is raised if the file is open in another application. The error does not mention that the file is opened or in use.

    On Screen Error:

    TITLE: Microsoft SQL Server Management Studio

    Object reference not set to an instance of an object. (Microsoft.SqlServer.Prose.Import)


    BUTTONS:

    OK

    Stack Trace

    Object reference not set to an instance of an object. (Microsoft.SqlServer.Prose.Import)


    Program Location:

    at Microsoft.SqlServer.Prose.Import.BcpProcess.set_UseSimpleDataType(Boolean value)
    at Microsoft.SqlServer.Import.Wizard.PreviewPageController.OnActivate()
    at Microsoft.SqlServer.Management.TaskForms.SqlWizardPageController.OnFirstActivate()
    at Microsoft.SqlServer.Management.TaskForms.SqlWizardPageController.Microsoft.SqlServer.Management.TaskForms.ISqlWizardPageController.SetActive()
    at Microsoft.SqlServer.Management.TaskForms.ControllerPage.OnSetActive()
    at Microsoft.SqlServer.Management.SqlWizardFramework.WizardFramework.ActivatePage(NavigationItem item, NavigationDirection direction)
    at Microsoft.SqlServer.Management.SqlWizardFramework.WizardFramework.ActivatePage(Page page, NavigationDirection direction)
    at Microsoft.SqlServer.Management.SqlWizardFramework.WizardFramework.GoToPage(Page page)
    at Microsoft.SqlServer.Management.SqlWizardFramework.WizardFramework.OnNext()
    at Microsoft.SqlServer.Management.SqlWizardFramework.WizardButtonsPanel.OnNext(Object…

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

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Data Collector 2017 exception 0xc0000409

    We receive this error when attempting to run the data collector for Sql Server 2017 CU11

    Faulting application name: dcexec.exe, version: 2017.140.3038.14, time stamp: 0x5b9c1fca
    Faulting module name: DTS.dll, version: 2017.140.3038.14, time stamp: 0x5b9c1f91
    Exception code: 0xc0000409
    Fault offset: 0x00000000001437f4
    Faulting process id: 0xd38
    Faulting application start time: 0x01d454f46156026f
    Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Binn\dcexec.exe
    Faulting module path: c:\Program Files\Microsoft SQL Server\140\DTS\Binn\DTS.dll
    Report Id: 09692622-b45f-4a7c-8951-6ac410174dbf
    Faulting package full name:
    Faulting package-relative application ID:

    Strangely, the Query Statistics collection runs without issue, but the Disk Activity and the Server Activity collection sets will not run.

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

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add SubSystem Property to Get-SqlAgentJobStep Default Output

    Please add the SubSystem property to the default output of the Get-SqlAgentJobStep cmdlet. Adding this to property to the default output will make it more obvious to customers that they can easily filter their results when searching for things like 'Jobs which contain a Step-Type of SSIS package'.

    (Please also consider making the Name property 10-charachters wider by default.)

    2 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 →
← Previous 1
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base