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. SQL Failovers slow down on Large Memory Systems

    We are running SQL Server 2017 Enterprise and utilizing AlwaysOn Availability Groups. We have several VLDB’s that contain different multi-TB tables partitioned across many filegroups. As such, some of our databases have in excess of 50 files and reside on servers with 1+ TB of RAM. Due to the size of memory allocation and number of files, we have found it can take in excess of 40 seconds for the primary replica to come online following a failover.

    This issue has been confirmed by Microsoft as “is by design” and is a known scenario under the following conditions:
    1. Your…

    42 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

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

    30 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. SqlPackage.exe plus _BIN2_UTF8 collation generates invalid BACPAC

    When a database has a char column with a _BIN2_UTF8 collation, SqlPackage for Windows export generates a BACPAC file that SqlPackage .NET Core fails to import.

    This problem can manifest as various error messages. The one that I have seen most often is, reformatted for clarity:

    Exception System.FormatException: Unexpected end of stream encountered.
    with Data:
        annotation_tableName=[core].[ObjectChangeType],
        DacLogContext_EntryId=bbd5810d-0795-4e0a-8a82-a34e58f1f72a
    at Microsoft.Data.Tools.Schema.Sql.SqlClient.Bcp.ColumnSerializer.ReadBytes(BinaryReader reader, Int32 len, Byte[]& bytes)
    in F:\B\16846\6200\Sources\Product\Source\SchemaSql\SqlClient\Bcp\ColumnSerializer.cs:line 100
    

    The stack trace suggests a problem in BCP file (de)serialization. Indeed, there is a difference in the BCP files generated by SqlPackage for Windows vs. SqlPackage .NET Core. For a char(1) Latin1_General_100_BIN2_UTF8 column…

    17 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. Sort Thread Numbers Correctly in Operator Properties

    Thread numbers do not sort correctly after you hit 10 threads.

    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

    1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  5. Statistics histogram bug with full scan/incremental stats not capturing all range values

    We're seeing some situations where the histogram for full scan incremental stats does not capture the full range of values in a given column. This is unexpected given the stats were created by looking all the rows in the table and is leading to situations where we see poor row estimates.

    Attached is a reproduction script that demonstrates this issue. A few additional comments:
    - I did play around with different sample rates and distributions of data, and this issue doesn't seem to be consistent. As an example, going from full scan to 1% sample rate for the incremental stat…

    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

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. SYSDATETIMEOFFSET precision decreased on Azure SQL

    SELECT SYSDATETIMEOFFSET()

    When I run the query on a local SQL Server 2019 instance, I get values like this:

    2021-03-24 14:32:32.5811589 -05:00
    2021-03-24 14:32:37.8169216 -05:00
    2021-03-24 14:32:42.6465055 -05:00

    When I run the query on an Azure SQL database, I get values like this:

    2021-03-24 19:31:04.6733333 +00:00
    2021-03-24 19:31:15.8300000 +00:00
    2021-03-24 19:31:20.4866666 +00:00

    In the latter, the last 5 digits are always repeating values. The value is less precise (or do I mean less accurate?) when the function runs on Azure SQL. Why is the behavior different?

    The documentation for SYSDATETIMEOFFSET says:

    SQL Server obtains the date and time values by
    9 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 →
  7. New "String or Binary data would be Truncated" message mangles value when join is used.

    I have found an issue with the value reported when a String or Binary would be Truncated" message occurs. I could not attach a test script that demonstrates the problem, so I have pasted the script below. If you comment the join in the final query, the value that is displayed in the error message is correct. If you add the join back, then the value is mangled.

    drop table if exists #inputTable;
    drop table if exists #outputTable;

    declare @longTestValue varchar(150) =
    'blahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblah';

    declare @shortTestValue varchar(150) = 'shortervalue';

    declare @parts table
    (
    PartId int
    );
    insert into @parts values (1),(2);

    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

    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  8. Procedure shutdown server

    Wrong procedure shutdown SQL server 2014/2016, if run it twice.

    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  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. SSAS tabular process full mistakenly reports error "Cannot order by ..."

    Our tabular database contains ~3e10 rows in the fact table.
    A ProcessFull sometimes reports mistakenly the error "Cannot order ''[] by [] because at least one value in [] has multiple distinct values in [].", without any names in the brackets.
    We verified all columns with "sort by column" property set to another column (select * from $SYSTEM.TMSCHEMA_COLUMNS where SortByColumnID>0) and all these column return a single value:

    select v.ColumnName, count(distinct v.SortColumnName)
    from olap.vViewName as v
    group by v.ColumnName
    having count(distinct v.SortColumnName) > 1

    Sometimes, without any changes to the underlying data, the process full finishes without any errors.

    So…

    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  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  10. Memory Mapped Write Failed error on SQL Server 2019 with Linux

    I am getting "memory mapped file write failed" error on Transactional Replication Snapshot agent. I am using Microsoft SQL Server 2019 (RTM-CU10) installed on a Linux Server. Tried many solutions but not able to fix this error.

    Snapshot agent is working properly for tables with few rows.

    Can you please check and revert?

    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 →
  11. SQL Server 2016/2017/2019 reproducible memory leak scenario with spatial index search - is there a patch?

    I found out that searching geography points with spatial index may lead to irrecoverable memory leak scenario, that is after some long running time only SQL Server restart helps and performance of SQL Server is severly degraded. Is there a patch for it or workaround? How it could go unnoticed?

    I've attached a reproduction script, it may be overwhelming but I'm just not sure which part is causing the leak actually. After several hours the script may lead to performance issues so please don't run it on production servers!

    REPOSTED FROM: https://docs.microsoft.com/en-us/answers/questions/288755/sql-server-201620172019-reproducible-memory-leak-s.html

    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

    6 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. Schema binding seems to not be enforced for view doing temporal query

    Originally posted on stackexchange, submitting a bug here now. (https://dba.stackexchange.com/questions/287616/schema-binding-seems-to-not-be-enforced-for-view-doing-temporal-query)

    I am using Microsoft SQL Server 2019. There are two strange behaviors that I don't see documented (if it is, please point me to the Microsoft docs link), I suspect they're related.

    1. The INFORMATIONSCHEMA.VIEWCOLUMN_USAGE system view does not show information about view queries that do temporal queries.

    2. If I create a view which does a temporal query, schema binding is not enforced. I can alter the columns on the underlying table that the view's query uses. Normally, creating the view with the "WITH SCHEMABINDING" option would…

    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

    2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  13. Power BI Report Server (Oct 2020) changes "changed by" date before modification

    Given a Power BI dashboard on Power BI Report Server with a direct query connection to an analysis service cube. Each invokement of manage in the browser leads to a change in the "changed by" date just before any modification takes place.
    This does not happen with import queries.

    15 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 →
  14. Actual plans CPUTime and ElapsedTime do not match SET STATISTICS TIME ON

    When I do a long-running query, the CPU & elapsed time from SET STATISTICS TIME ON does not match the actual execution plan.

    For example, in this live stream: https://www.youtube.com/watch?v=yJgwQP84PdE

    I ran this query from one of the large Stack Overflow databases: SELECT COUNT(*) FROM dbo.Posts;

    The actual plan: https://www.brentozar.com/pastetheplan/?id=B1KzQ42Wv

    The statistics TIME output:
    SQL Server Execution Times:
    CPU time = 55968 ms, elapsed time = 51474 ms.

    31 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 →
  15. Invalid class string when opening maintenance plans in SSMS 18.9.1

    Possible bug:
    When opening a maintenance plan in SSMS 18.9.1 from a remote server, I get an "Invalid class string" error.
    Also states "Value cannot be null.
    Parameter name: component (System.Design)"

    If I run 18.8 on the server directly or remotely, I have no issue opening the plans.

    1 vote

    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 →
  16. bug starting from sql 2017, multistatement function kills connection in case of timeout

    timeout multistatement function kills connection in case of timeout

    problem with sql 2019 (works ok on sql 2014)

    create database test1
    go
    use test1
    go
    set nocount on
    go
    create table OneBigTable1 (a int, b int)
    go
    declare @a int = 0 while @a < 10000 begin insert into OneBigTable1 select @a, @a & 255;set @a = @a + 1 end
    go
    SET ANSINULLS ON
    GO
    SET QUOTED
    IDENTIFIER ON
    GO
    CREATE or alter FUNCTION dbo.testkill03()
    RETURNS @RET TABLE (
    A int
    )
    BEGIN

    declare @A int;
    select @A = count(1) from OneBigTable1 b1
    inner loop join
    1 vote

    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 →
  17. Index was outside the bounds of the array.

    v18.9.1. When right-clicking and choosing New Database Diagram from within a database with existing diagrams, sometime I receive this error.

    SQL Server version is 12.0.6164.21

    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  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. Azure Synapse: Merge command with the identity column in target table is not working

    The Merge command on the target table with the identity column gives an error although we are not updating/inserting the identity column. Please find the below snippet and error message

    Msg 8102, Level 16, State 1, Line 7
    Cannot update identity column 'id'.

    CREATE TABLE dbo.t1 (id INT IDENTITY(1,1), Sub INT, Metric INT) WITH (DISTRIBUTION = HASH(Sub), CLUSTERED COLUMNSTORE INDEX);

    WITH SRC AS (
    SELECT 1 AS Sub, 100 AS Metric)
    MERGE dbo.t1 AS tgt
    USING SRC ON tgt.Sub = SRC.Sub
    WHEN MATCHED THEN UPDATE SET Metric = SRC.Metric
    WHEN NOT MATCHED THEN INSERT (Sub, Metric) VALUES (SRC.Sub, SRC.Metric);

    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

    4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. 1 vote

    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 →
  20. High DPI monitors

    Still does not do proper scaling on high DPI monitors. Even the old version 17 did it correctly.
    Using

    Version 18.9.1

    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 →
← Previous 1 3 4 5 286 287
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base