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 18.5 Generating Scripts

    I noticed in version 18.5 that when I edit a view by choosing right click the view - script view - alter to - new sql window, it generates a change script (see attached). I am not aware I turned on this feature and I can't figure out how to turn it off. I have ssms Options - Table Designer - Tracking unchecked so I don't know where else to look. I uninstalled and reverted back to 18.1 and 18.4 and the change script code doesn't run before the view comes up to alter in the sql window so I…

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

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Change execution plan terminology

    SQL Server has since almost forever used the terms "Actual Execution Plan" and "Estimated Execution Plan" for execution plans with and without added run-time counters. And this has since almost forever caused confusion and misunderstanding.

    Erin Stellato, Grant Fritchey, and me, with the help of Pedro Lopes, have prepared a proposal for better terminology. Terms that better describe the reality and have less chance for confusion.
    See https://sqlserverfast.com/blog/hugo/2020/02/stop-the-name-calling-execution-plan-terminology/ for a more detailed explanation.

    Together with Erin and Grant, I request Microsoft to change the terminology in their tooling. In the next release of Management Studio, please replace "Estimated Execution Plan"…

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

    We’ll send you updates on this idea

    unplanned  ·  7 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  3. ROUND FLOAT BUG

    -- Microsoft SQL Server 2017 (RTM-CU18) (KB4527377) - 14.0.3257.3 (X64)

    SELECT ROUND(CAST(5.175 AS FLOAT),2)
    return 5.17 -- good is 5.18

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

    We’ll send you updates on this idea

    unplanned  ·  3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. sys.time_zone_info shows incorrect values for current_utc_offset and is_currently_dst for GMT Standard Time

    This query:
    SELECT * FROM sys.timezoneinfo WHERE name = 'GMT Standard
    Time'

    Returns +01:00 and 1, respectively, for currentutcoffset and iscurrentlydst, which is not correct.

    We know this is incorrect due to the explanation on: https://www.timeanddate.com/time/zones/gmt
    which states:
    "Greenwich Mean Time (GMT) has no offset from Coordinated Universal Time (UTC)."
    The site also states:
    "Some places observe daylight saving time/summer time during the summer, and therefore use IST (Irish Standard Time) or BST (British Summer Time) in the summer."

    This repros on SQL 2017 RTM-CU16 (KB4508218) 14.0.3223.3, running on Windows Server 2016 1607 (14393.3204),…

    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 →
  5. Color for defined variables

    Currently defined variables "@Example" fall under the 'Identifer' category as far as custom colors in the text editor is concerned and I would like for them to be able to be distinguished. I am asking for them to be broken out as a different category so they can be customized (I basically want them to stand out so I can more easily see where they go without having to do a search for "@" etc.)

    1 vote
    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 →
  6. 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 →
  7. UTF-8 in SQL 2019: Add Turkish_100_BIN2_UTF8 collation to handle Turkish / Azeri case mappings for "i" and "I"

    This is an extension of the following item:

    "UTF-8 in SQL 2019: Binary UTF-8 Collations are missing" ( https://feedback.azure.com/forums/908035-sql-server/suggestions/35583976-utf-8-in-sql-2019-binary-utf-8-collations-are-mis )

    Currently, SQL Server 2019 (as of CTP 3.0, at least) has a single binary collation: Latin1General100BIN2UTF8 . While it is entirely appropriate to not have a "BIN2UTF8" collation for each culture, there is still something missing that cannot be done using the "Latin1General100BIN2UTF8" collation: uppercase "i" to "İ", and lowercase "I" to "ı".

    The following query demonstrates this:

    SELECT UPPER('i' COLLATE UzbekLatin100CSASKSWSSC) AS

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  8. CREATE OR ALTER is not fully supported in Transactional Replication DDL commands

    We've been having trouble with some objects not replicating correctly after a DDL change.

    When a published function or proc is altered, the following appears to happen:
    A database trigger is called: trMStranalterschemaonly
    Which calls a proc called: sys.spMStranddlrepl - This proc will output debug IF MSrepldebugDDL exists (create anything called this!)
    which calls a function: master.sys.fn_replgetparsedddlcmd, which is designed to return the ddl after the object's name, to be used for generating the command to be applied 
    at the subscribers.

    SQL Server BOL states that ALTER is supported (https://docs.microsoft.com/en-us/sql/relational-databases/replication/publish/replicate-schema-changes?view=sql-server-2016)

    However, this doesn't…

    8 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 →
  9. SQL Server Management Studio 2018: bad icon

    The icon for SQL Server Management Studio 2018 blends in with the default windows 10 start menu tile background. This does not look very good.
    The SSMS 2017 icon had a white outline around the little crossed tools, so that you could still see things regardless of the colour of the tile background

    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 →
  10. SQL Import and Export Wizard

    I have been using SQL Server since it was born and the Import Wizard has consistently had issues with registrations of file types and transformations. In this day and age of AI, ML and exotic claims of smart technology I find it difficult to believe that this import "Wizard" still requires me to go through hoops to determine registration requirements and combinations and permutations of possible formatting issues. This has got to be one of the dumbest "Wizards" out there and maybe can get some loving and caring in the next release. Cheers Peter Molloy

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make SSDT Available for Linux as well

    As of now, if we need to build the SQL Server project, we need the SSDT toolkit on a Windows machine to build the project. Is it possible to make it available for Linux as well so that we can build the SQL server project not only on Windows but on Linux as well?

    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 →
  12. Change the title of a report to be different from .rdl file name

    If my RDL file is named Reportforseeingthings.rdl

    Displayed the web portal report title as "Report for seeing things"

    This would allow users to adhere to URL design best practices and give designers the ability to accomodate their clients naming pattern requests.

    3 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 →
  13. Dark Theme in DevOps ignores color in textboxes

    The Dark Theme for DevOps works nicely in general, but text in textboxes does not show font color/background color.

    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. Add backup configuration to the setup process for SQL Server.

    What I’m asking for (besides you to upvote that User Voice item) is for Microsoft, as part of SQL Server setup, to add two new screens. The first would be called “Backup”—it would offer a dire warning to the effect of:

    In order to protect the data in your databases, Microsoft strongly encourages you to take backups of your data. In the event of hardware failure, data corruption, or malicious software, Microsoft support will be unable to help you recovery your data, and you will incur data loss. This box is checked by defaults to enable automatic daily backups of…

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

    We’ll send you updates on this idea

    0 comments  ·  Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Adding Multi-column IN clause support by SQL Server

    Currrently, SQL Server does not support multi-column IN clause. For example, the following query :
    Select * from tableA where (columnA, columnB) in select (columnX,columnY) from tableB
    will not run, failing by displaying the error :
    non-boolean type specified in a context where a condition is expected”

    2 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. SQL Server Data Import and Export Wizard: When "Delete rows in destination table" is chosen, don't attempt to Truncate the table

    When this option is chosen, the Import/Export Wizard actually does a Truncate on the selected table. This will fail when there are any foreign key constraints on the table, with the following error message.

    Executing the query "TRUNCATE TABLE {tablename}
    " failed with the following error: "Cannot truncate table '{table
    name}' because it is being referenced by a FOREIGN KEY constraint.".

    There's a disconnect between what the UI says it will do (DELETE) vs. what actually happens (TRUNCATE).

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. SQL Server Data Import and Export Wizard: Order of Tables

    When using the Import/Export wizard to copy multiple tables from one DB to another, it would be great if SQL Server could intelligently determine the order to process the tables based on foreign key constraints.

    With the current behavior I will often get foreign key constraint failures because data is loaded into a child table before the data is loaded into the parent table.

    It should be possible to determine an optimal load order by using the foreign key constraints defined on the tables. If not, then it would be nice to be able to manually set the order.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  0 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  18. UTF-8 in SQL 2019: Collation Precedence allows for silent truncation (data loss) implicitly converting Extended ASCII characters into UTF8

    In SQL Server 2019 CTP 2.1, VARCHAR data being implicitly converted from a non-UTF-8 Collation into a UTF-8 Collation can be silently truncated when Extended ASCII characters in being used (i.e. characters with values between 128 and 255). Standard ASCII characters (values 0 - 127) are not affected since they are 1 byte whether they are in a UTF-8 Collation or not. But Extended ASCII characters (i.e. those that change per each Code Page) are never 1 byte: they are usually 2 bytes (and possibly 3, though I'm not sure about this and haven't tested all of them).

    The problem…

    2 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 →
  19. UTF-8 in SQL 2019: Collation Precedence allows for Unicode character data loss concatenating UTF8 with higher precedence non-UTF8 VARCHAR

    In SQL Server 2019 CTP 2, if you have UTF-8 data and concatenate that with another VARCHAR value of a higher Collation Precedence, and having a non-UTF-8 Collation, the Code Page will change to that of the other Collation. And since a) that other Collation is a non-UTF-8 Collation, and b) the datatype is still VARCHAR, any characters that do not have a best-fit mapping in the destination Code Page will be converted into one or two "?"s (depending on if the character is BMP or Supplementary).

    To be fair, this scenario already existed, to a degree, when doing similar…

    2 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 →
  20. UTF-8 in SQL 2019: Inconsistent handling of invalid UTF-8 byte sequences

    In SQL Server 2019 CTP 2, when inserting invalid UTF-8 byte sequences into VARCHAR types that are using a "_UTF8" Collation, you will sometimes get an error, and at other times that operation will succeed and you will have a string showing "unknown" characters.

    For example, inserting 0x80 by itself fails. But inserting something along with it can work (anything that is not more of 0x80). And, inserting 0x90 by itself, also invalid, does not fail.

    This might be related to another bug I just filed: Invalid UTF-8 bytes get (Msg 682, Level 22, State 148) Internal error. Buffer provided…

    1 vote
    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 →

    Thank you for providing the examples of handling invalid characters. While we are trying to detect invalid sequences as we encounter them, at the same time we need to be cautious about performance. As such the current behavior occurs by design, under the general principle that if a partially invalid character sequence is input but certain characters were valid, the valid part of the character sequence may be output without error. If a fully invalid sequence is input, an error is then generated. This doesn’t mean that the logic of handing damaged sequences cannot be improved, so we encourage you to share your suggestions on how to make it better.

← Previous 1 3 4 5 134 135
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base