Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

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 Microsoft Q&A or Stack Overflow

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. "Edit Query Text" query text doesn't match the actual query in 2017 RTM

    In 2016 & prior versions, when looking at a stored procedure's execution plan, if you right-click on the plan and click Edit Query Text, you get the full text of a stored procedure. In 2017, it's clipping out parts of a stored procedure, and formatting the query differently.

    33 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. SQL 2019 15.0.2070.41: Out of memory, page allocation fails when using Scalar-valued function in Where -clause

    Instance crashes to OOM using Scalar-valued functions when Scalar UDF Inlining is turned ON and function is used on WHERE -clause. Not dependent on SQL memory as it always consumes all memory available to instance.

    Simple function (i.e returning date) fails when used on WHERE clause and page allocation from MEMORYCLERKSQLOPTIMIZER allocates all memory even with fresh database when TSQL-SCALARUDF_INLINING is ON.

    Working query with function:
    declare @dt as datetime='2019-12-01'
    declare @dt2 as datetime='2019-12-20'
    declare @d as datetime = dbo.datereturn(@dt2,'ENDOFDAY')
    select * from TABLE where field_date between @dt and @d

    Broken query with function in WHERE -clause:
    declare…

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. SQL Server 2019 scalar functions fail incorrectly if they have a CHECKSUM

    Scalar functions with CHECKSUM(*) fail on compatibility level 150, SQL Server 2019 build 15.0.4043.16.

    ALTER DATABASE CURRENT SET COMPATIBILITY_LEVEL = 140;
    GO

    CREATE OR ALTER FUNCTION dbo.Test()
    RETURNS INT AS
    BEGIN

    DECLARE @i BIGINT;
    
    SELECT TOP 1 @i = CHECKSUM(*)
    FROM master.dbo.spt_values;
    RETURN 1;

    END
    GO
    SELECT dbo.Test(); / Works fine /

    ALTER DATABASE CURRENT SET COMPATIBILITY_LEVEL = 150;
    GO

    SELECT dbo.Test();

    /* Gets error:

    Msg 1789, Level 16, State 1, Procedure Test, Line 6 [Batch Start Line 17]
    Cannot use CHECKSUM(*) in a computed column, constraint, default definition, or INSERT statement.

    */

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. SQL Server Management Studio - search interface bug, crashing SSMS

    There is a bug in SQL Server Management Studio (17.9 and all below) that force the application to crash/restart. In order to reproduce follow the steps below:


    1. Select database from the object explorer

    2. Press F7 to open Object Explorer Details window and perform a search to object

    3. After the search completes, select the object, right click on it and then click "synchronized" from the menu.

    4. Then click the BACK button several times (fast). You will get the following error:

    "There is already a commandd handler for the menu command 'guid goes here: 189."

    After several clicks somewhere other the SSMS…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. ENABLE_PARALLEL_PLAN_PREFERENCE

    Document and make it officially supported a new ENABLEPARALLELPLAN_PREFERENCE query option, released in SQL Server 2016 SP1 CU2

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. SSDT Schema Compare

    SSDT Schema Compare does not provide an option when generating a script to perform IF EXIST. This would be a nice enhancement to allow for scripts to be re-run if necessary.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  8. SSMS 18.2 - Can't copy text from find and replace window

    When I try to copy text from the find and replace window it fails with the message: "Unsaved documents cannot be cut or copied to the clipboard from the Miscellaneous Files project. You must save the unsaved document(s) before cutting or copying them." See attached screenshot.

    Text in the find/find and replace windows should always be copyable, regardless of whether the document has been saved or not.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Unfortunately this is a bug coming from the underlying Visual Studio core. There is a workaround to enable the functionality, however – under Tools menu>Options item>Environment section>Documents tab – uncheck the item for “Show Miscellaneous files in Solution Explorer”. After unchecking the option, restart SSMS.
    I will add this note to the docs as well.

    thank you!

  9. Dark theme ignored in Object Explorer

    Dark theme created from Settings file attached.
    All windows except object explorer have dark background.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  10. Port Microsoft Connect Upvotes

    Now that Microsoft Connect is gone, and all of the suggestions have been moved here, why didn't the upvote count move as well?

    Is this just Microsoft's way of sweeping the old suggestions under the carpet, by ignoring the previous upvotes and restarting allof the items back to 0?

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    UserVoice didn’t have a way to “set” upvotes during an import. So we didn’t have a choice. To help mitigate that, we did add the UpVote count into the comments. Although unsearchable, we did what we could to preserve that data.

    As for preserving the names, that would have meant exporting user information from a system owned by Microsoft and importing it into a system owned by a 3rd party – which goes against our Privacy Statements. As much as we would have wanted to preserve acknowledgements and credit, we needed to scrub those out.

  11. Make a MacOS version of SQL Server Management Studio

    I really like SQL Server Management Studio but I strongly wish there was a version of it for the Mac OS.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  12. data compression SMO bug

    Setting the datacompression to 'None' for indexes doesn't work. Objects are left with the compression setting they had prior.

    Reproducible with the following code

    $server = Connect-DbaInstance -SqlInstance server1
    $table = $server.Databases['test'].Tables['table']
    $index = $table.Indexes['CL_table']

    $index.PhysicalPartitions[0].datacompression = 'Page'
    $index.Rebuild()

    $index.PhysicalPartitions[0].datacompression = 'Row'
    $index.Rebuild()

    $index.PhysicalPartitions[0].datacompression = 'None'
    $index.Rebuild()

    The SQL executed (captured with xevents) is below:

    ALTER INDEX [CLtable] ON [dbo].[table] REBUILD PARTITION = ALL WITH (PADINDEX = OFF, STATISTICSNORECOMPUTE = OFF, SORTINTEMPDB = OFF, ONLINE = OFF, ALLOWROWLOCKS = ON, ALLOWPAGELOCKS = ON, FILLFACTOR = 100, DATACOMPRESSION = PAGE)
    ALTER…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  13. SQL Server Management Studio 18 GA (15.0.18118.0) not compatible with .NET Framework 4.8

    Windows 10 1903 - SSMS 18 does not start.
    Windows Server with .NET Framework 4.8 - SSMS 18 does not start.

    AppData\Roaming\Microsoft\AppEnv\15.0\ActivityLog.xml:
    ...Could not load file or assembly <Microsoft.VisualStudio.Shell.Interop.8.0, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a>...

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    closed  ·  17 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  14. SSMS RESULT GRID TIP: Add Excel like quick tip for SUM, COUNT, MIN, MAX, AVG

    in next update kindly add Excel like quick tip feature to show SUM, COUNT, MIN, MAX, AVG on SSMS status bar for selected ROWS, COLS, or CELLs.. This feature would be a great help!

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  15. SSMS Automatic Updates

    When there is a new update for SSMS, notifications pop up on the desktop and following the notifications through leads to the SSMS update window, then the user has to download a whole new package (~800mb) before reinstalling over the current (older) installation of SSMS.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  16. SSMS 17.2 error launching 'Analyze Query in Database Engine Tuning Advisor', 'Object must implement IConvertible. (mscorlib)'

    SQL Server 2016, 13.0.4435.0, SSMS 17.2, database is SQL 2012 compatibility

    The argument type 'server type = Sql, server name = SomeName, timeout = 30, database = inSight_10x, protocol = NotSpecified, workstation = , integrated security = True' cannot be converted into parameter type 'Microsoft.SqlServer.Management.Common.SqlConnectionInfo'. (mscorlib)


    Program Location:

    Server stack trace:
    at System.Runtime.Remoting.Messaging.Message.CoerceArg(Object value, Type pt)
    at System.Runtime.Remoting.Messaging.Message.CoerceArgs(MethodBase mb, Object[] args, ParameterInfo[] pi)
    at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ISessionController.CreateSessionFromQuery(SqlConnectionInfo connectionInfo, String sqlQuery, String batchSeparator)
    at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.SqlScriptEditorControl.OnDatabaseTuningAdvisor(Object sender, EventArgs a)

    ===================================

    Object must implement IConvertible. (mscorlib)


    Program Location:

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Import Flat File does not allow import of bit when values are 0 or 1 in SSMS 17.3

    When I import a file that uses 1 or 0 as true and false the import fails because it cannot convert 1 or 0 to a BIT. Here is the error that is returned. To make this work I changed the columns to TINYINT. After the table is populated I altered the columns to be BIT and it completed successfully.

    TITLE: Microsoft SQL Server Management Studio

    Error inserting data into table. (Microsoft.SqlServer.Import.Wizard)


    ADDITIONAL INFORMATION:

    Error inserting data into table. (Microsoft.SqlServer.Prose.Import)


    The given value of type String from the data source cannot be converted to type bit of the specified target…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. SSMS restore files to wrong locaton

    When adding a replica to an availability group using Full backup option generates wrong code. The database restore on the destination server is generated with the Move option, and database files are restored to the destination sql-server default file location instead of the original files location of the source server.

    This seems to be a "new feaure" in SSMS 17.2 and onwards as older SSMS' do it right.

    All documentation still says that filepath must match on all replica servers!

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your patience. I have created a tracking item in our content VSTS issue tracking system. For the most part, feedback can be made directly to our topics as our new documentation platform supports comments directly on the topic.
    https://docs.microsoft.com/en-us/sql/sql-server/sql-server-technical-documentation

    As well as you can edit the topic yourself by clicking the “Edit” button on the topic. For help in editing, see https://docs.microsoft.com/en-us/sql/sql-server/sql-server-docs-contribute.

  19. Support Drag and Drop table name and column name in Query editor - Azure Data Studio

    Azure Data Studio

    Drag and drop is available in SSMS and is very handy specially when you need all column names and not going to type them individually.

    Another option would be a shortcut key for inserting the actual column name instead of the *

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  20. SSMS tab history

    SSMS 17 - Add option to NOT autoconnect restored query editor tabs, or at least background them so that SMSS is usable sooner.

    On startup, restoring previously open query editor tabs is great. However, if there are many, it can hang the startup procedure for minutes. It would be great to disable or background the autoconnect of these restored tabs so that we can get working sooner.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 10 11
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base