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. 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 →
  2. Visual Studio 2017 SSDT adds hardcoded master.dacpac include

    Visual Studio 2017 seems to add a hardcoded path to the master.dacpac if I include it in a project of mine. Older versions of the SSDT used the $(DacPacRootPath) variable to get the master.dacpac.

    This is really annoying as it breaks the builds on our build server where the master.dacpac is installed in a different folder than on my development machine.

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

    We’ll send you updates on this idea

    12 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. SSMS Crash when dragging table from Object explorer into new query window

    Have just installed this version v18.1 and everytime I drag a table from Object explorer into new query window SSMS crashes, I have to kill it.
    I have no add-ins installed, have rebooted since installing.

    O/s Win 10 15063.1387

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

    We’ll send you updates on this idea

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

    34 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  5. SSMS 18.0 GA can't be installed

    When I'm trying to install SSMS 18.0 GA, I get error: "SSMS can only be upgraded by installing the package of the matching language. Please, use the matching version of the installer, or uninstall the current version of SSMS and run SSMS setup again." And I'm not alone: https://social.technet.microsoft.com/Forums/en-US/16d0e279-6ff4-4d5f-ad0a-5039235f03b9/ssms-2018-setup-blocked?forum=sqltools

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

    We’ll send you updates on this idea

    24 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    I’m looking into this issue.

    In the meanwhile, could you take a look at the SSMS setup logs (%TEMP%\SSMSSetup\SSMS-Setup-ENU_20190430231104.log). I’m interested in the lines in the range 133-216. Could you share those (tip: have a look at the lines and sanitize them, if you think they may contain sensible information?

    Also, if you could share the output of:
    reg query “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32 /s

    And, finally, to unblock yourself:
    1) Make sure you don’t have any previous version (RC, Preview) of SSMS 18.0 installed (check Add/Remove programs; if you do, uninstall it)
    2) Make sure “C:\Program Files (x86)\Microsoft SQL Server Management Studio 18” does not exist (if it does, the delete it)
    3) Delete the mentioned registry key (e.g. by running from an elevated cmd prompt:
    reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32)
    4) Retry setup
    Please, let…

  6. Restore CTRL-D shortcut for ResultsToGrid in SSMS

    In SSMS 18 Preview 4, the default binding have changed to Edit.Duplicate lines, quoting https://feedback.azure.com/forums/908035-sql-server/suggestions/32896594 as a the motivation.

    CTRL-D has been bound to ResultsToGrid, for almost 20 twenty years (that is since Query Analzyer came out in SQL 7.) That is engraved in many people's minds.

    Yes, I can change the key binding, but so can people who prefer to use it to duplicate lines.

    Please restore the original default. It does not serve the community to change existing bindings.

    28 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 →

    Note: this is a behavior that is only observed in SSMS 18.0 Preview 4.

    It turned out that the migration to the new VS2017 Shell in SSMS 18.0 ended up changing the binding for the CTRL+D, which accidentally was a request from a few other users.

    Due to popular demand (and also to preserve the old behavior), I’m going to bring back CTRL+D and have it bound to the ResultToGrid in the Query Editor.

    I’m going to bind the “Edit.Duplicate” to CTRL-K, CTRL+V, which is consistent with the current VS2017 behavior.

  7. Too Many Decimal-places in Size (MB) property

    The "Size (MB)" property in SSMS reports the size with way too many decimal places if the size is not divisible by 1024. This can make quickly understanding the sizes of your databases in Object Explorer Details frustrating. This is often seen if a database has auto-grown by a percentage value. If a customer wants to see a precise Size value for their database, it is better for them to use a query or possibly the built-in Disk Usage report. Please eliminate the displaying of any decimal values, or at least a maximum of one decimal-place, in the Size (MB)…

    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 →
  8. SSMS Install with SQL Server 2016 causes Device Manager conflict on VS location sensor driver

    If you take (as an example) a clean machine, with no VS or SQL Server yet, install SQL Server 2016 (say community but doesn't matter), Device Manager is fine, no conflicts (no VS location sensor driver yet)...Then you install SSMS (production/GA version 16.5.3), you get a Device Manager conflict (yellow exclamation mark/can't load driver error) on a new sensor entry called "Microsoft Visual Studio Location Simulator Sensor".

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

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Incorrect GrantedQueryMemory(KB) Value on SQL Performance Dashboard or SSMS17.9

    The inbuilt SQL Dashboard within newer versions of SSMS displays report for GrantedQueryMemory(KB) column for current request sub report. The value displays the wrong number as output displayed is in bytes while column says KB.

    I have verified using the dmv "sys.dm_exec_query_stats" which lists this number in no.of pages which later is converted to KB

    When checking within rdl file we can see that conversion is made with expression as =8192 * Fields!granted_query_memory.value which gets this value in bytes.

    Therefore we might need to change that expression to = 8 * Fields!granted_query_memory.value

    7 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 →
  10. SSMS 17.2 (and 17.1) Mirror configuration fails because mirror database is restoring

    Attempting to configure database mirroring through the SSMS 17.2 (and 17.1) GUI between two SQL 2016 servers fails with "Database 'Test' cannot be opened. It is in the middle of a restore."

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

    We’ll send you updates on this idea

    4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  11. SSMS 18

    When double clicking on an sql file, a new instance of SSMS 18 will start up, but the file never opens. This never happened when I was using SSMS 17.8. I'm running on Windows 10 OS.

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

    We’ll send you updates on this idea

    4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    This is indeed a known issue in SSMS 18.0 (up until Preview 6).

    I expect to have a fix in the next Preview.

    In the meanwhile, you can workaround it by doing this:
    1) Close SSMS
    2) Edit the following file …\Common7\IDE\Extensions\Application\ssms.Application.pkgdef by replacing
    “DDEApplication”=“ssms.18.0”
    with
    “DDEApplication”=“ssms.15.0”
    3) Save the file

    Thanks,
    -Matteo

  12. Add support for storing UTF-8 natively in SQL Server.

    You can store Unicode data in SQL Server today, but only in UCS-2 encoding. In many environments, UTF-8 is the dominating encoding for Unicode data, and it is the default
    encoding for XML documents.

    Today UTF-8 applications must convert between UCS-2 and UTF-8 to retrieve and store
    data in SQL Server, which adds complexity and overhead to applications.

    Another issue is that for languages written in the Latin script, UTF-8 is a much more effective storage format, since most for characters in text, only one byte is needed.

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

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  13. SSMS 18.1 still missing status bar colors

    I posted this bug in the early betas and requested it again to be fixed after GA release but in 18.1 there is still no change.

    The query status bar in SSMS 17 and older has been khaki for single server connections and pink for group connections. There is no color for either type in SSMS 18 and going into options and setting it to khaki and pink values is not retained after closing the app. This is very important indicator as a quick confirmation that I'm not in a milti-server query window before executing.

    Tools -> Options -> Text…

    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 →
  14. Appending datetime to the end of ""Commands completed successfully ... 2018-03-05 09:28:10.1829207"

    When I make any change to a stored procedure & compile it (F5),
    besides just returning ...
    "Commands completed successfully."

    Could we append a datetime to the end of that please ?
    "Commands completed successfully ... 2018-03-05 09:28:10.1829207"

    Buddy

    4 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 →
  15. SQL server Import and Export Wizard missing/disabled SSMS 18.0

    SQL Server import and export is disabled in SSMS 18.0, is this temporary and available in later versions of 18 or we wouldn't have import export going forward?

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

    This is indeed an unintended removal. It only affected SQLEXPRESS.
    Thanks for the reporting it.
    We’ll fix it in a future release of SSMS 18.×.

  16. Replication Monitor Crashing with SSMS 17.8.1

    I installed SQL Server Management Studio 17.8.1 last night. This is from the About box:

    Microsoft SQL Server Management Studio 14.0.17277.0
    Microsoft Analysis Services Client Tools 14.0.1016.262
    Microsoft Data Access Components (MDAC) 10.0.16299.15
    Microsoft MSXML 3.0 4.0 6.0
    Microsoft Internet Explorer 9.11.16299.0
    Microsoft .NET Framework 4.0.30319.42000
    Operating System 6.3.16299

    This build has broken Replication Monitor. When I go to review the details of (for example) Distribution Agent Job Properties, it will crash with "Could not load file or assembly 'Microsoft.AnalysisServices.AppLocal, Version=14.0.0.0"..... The located assembly's manifest definition does not match the assembly reference."

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

    We’ll send you updates on this idea

    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    It turned out that UserVoice clipped the XML snipped I published (although it is there; you just can’t see).

    I’ve updated the steps with instructions on how to download a new version of the .config file, so you don’t have to edit it.

    I apologize for the inconvenience.

  17. SMO Server class spams AGs with failed blank user logins when used with SqlCredential

    When using SMO with a SqlCredential it may hammer the target server with failed connections to a blank username. These can be found in the SQL ERRORLOG. Interestingly SMO still appears to work but this prevents SqlCredentials from being used in production because it would trigger hundreds of thousands of failed logins every day.

    The problem is caused because somewhere in SMO it is not detecting the SqlCredential correctly.

    This does not happen on standalone servers. It does happen on servers in an AG, even when the SQL principal has sysadmin, and even with the server is a primary.

    I've…

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

    We’ll send you updates on this idea

    started  ·  2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. SSMS Flat File Import is not working for SSMS 18.1 upgrade

    When upgrading SSMS 18.0 to 18.1, the Flat File Import is no longer importing csv, tab delimited or other delimited files.

    Procedure:

    1. Open SSMS 18.1, select any database to import to.
    2. Right click | Task | Import Flat File
    3. When presented by the file browse of the Wizard, navigate to where the attached (test_csv.txt) and load
    4. The attached (flat_file_import_error.png) appears.

    note: This looks to be happening in my machine, as a fresh install SSMS 18.1 instead of an update on a different machine works.

    Attached:
    flat_file_import_error.png - screenshot of error
    test_csv.txt - sample csv used
    ssmssetup_logs.zip…

    2 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 →

    Thank you again for reporting this issue, we have discovered this upgrade issue is caused by a dll that was not updated during the upgrade process. There are 2 work around options for now and the upgrade scenario will also be fixed in the next release of SSMS.

    Option 1) Replace the problem dll which by default is located at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Extensions\Application\Microsoft.SqlServer.Prose.Import.dll with the new dll and then Flat File Import will work. You can get that dll either from a clean install of SSMS 18.1 or we have uploaded the new dll here for convenience https://1drv.ms/u/s!BCzXOqHzD6izqp9zjQpa1nGpcgvuuw?e=XDfQau

    Option 2) Uninstall and reinstall SSM 18.1 as the full install will bring the correct dll

    Thank you
    Erica

  19. SSMS 18.0 - New Job Schedule Window Month Control Covered at High DPI

    At 175% DPI the month control is covered by a gray box and the value inside can't be seen.

    See attached screenshot.

    2 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 →
  20. SSMS 18 fails to install when log path contains spaces

    When executing SSMS-Setup-ENU.exe with the /Log argument that points to a directory path that contains spaces, the install fails.

    This appears to be because the quoted log path is not passed correctly to VSTS_setup.exe.

    Compare the two extracts from install log files. The first fails, whereas the second succeeds.

    [43E0:4374][2019-04-29T14:01:56]i301: Applying execute package: VSTA2017, action: Install, path: C:\ProgramData\Package Cache\BBABC3362FBBB5C3B3543B252A5D7E5C9D9E6B36\redist\vsta_setup.exe, arguments: '"C:\ProgramData\Package Cache\BBABC3362FBBB5C3B3543B252A5D7E5C9D9E6B36\redist\vsta_setup.exe" /q /norestart /log C:\Users\David\AppData\Local\Temp\\chocolatey\\SQL Server Management Studio\SQL Server Management Studio.MsiInstall_6_VSTA2017.log'
    [43A4:43A0][2019-04-29T14:01:56]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
    [43A4:43A0][2019-04-29T14:01:56]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
    [43A4:43A0][2019-04-29T14:01:57]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 50
    [43A4:43A0][2019-04-29T14:01:57]i000: MainViewModel.OnPackageActionProgress: Percent completed:…

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

    We’ll send you updates on this idea

    started  ·  7 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

SQL Server

Feedback and Knowledge Base