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. Error with Detail Rows Expression when used with Excel drillthrough

    With a SSAS Tabular model on compatibility Level 1400, I have defined a Default Rows Expression to allow the client to obtain specific columns when connecting with an Excel pivot table but in Excel 2016 the following error is returned when the drillthrough is executed:

    "RETURN clause cannot be used with the DRILLTHROUGH statement when a DetailRows expression is already defined on the measure 'Transaction Count'"

    I have defined the Default Detail Rows Expression at the table level and have not defined a Detail Rows expression on any measures individually. My understanding is that if no expression is defined on…

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

    We’ll send you updates on this idea

    under review  ·  6 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. SQL Server should not raise illogical errors

    You already have tons of these bug reports, and I bet that you have closed them all "by design" and told people to use the CASE statement. But, no, you are wrong. This is a bug, and should be fixed. Although the fix is to add new functionality, hang on.

    Consider this silly repro:

    create table albert(a int NOT NULL,

                        b varchar(23) NOT NULL)
    

    create table stina (a int NOT NULL)

    go
    insert albert (a, b)

       values  (1, '99'), 
    
    (2, 'Gurka'),
    (3, '89')

    insert stina (a) values(1), (3), (9), (12)
    go
    SELECT a.a, a.b + 100

    FROM albert a
    JOIN…

    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 →

    Upvotes: 82

    <=-=Mar 3 2010 10:44AM=-=>

    Hi Erland,
    Thanks for your feedback. We are aware of this request and hope to address it in a future version of SQL Server.


    Umachandar, SQL Programmability Team

    <=-=Jul 21 2010 5:36PM=-=>

    This bug cost me and others about 8 hours of troubleshooting this week. And the query was working until statistics were updated. That’s the spooky part, that a new join order can cause an error in a previously-working query. This was compounded by the fact that the query was in a UDF and 1) error messages don’t list the line in the UDF but rather the calling SP and 2) I know of no way to see the execution plan of a UDF, which would have helped because I could have seen in the plan the conversion to float before the JOIN to the filtering table.

    <=-=Mar 9 2011 12:08PM=-=>

  3. SSMS / Management Studio shows wrong decimal separator

    When the regional settings of the computer has , as decimal separator, management studio will use it to format float -columns, but for decimal(x,x) it still uses . instead. This is quite annoying since . is used as a separator in dates, so copying data into excel tries to turn numbers into dates.

    This same issue exists at least in all versions from 2005 up to 2016 CPT2. I think there was a connect item for this earlier too, but I can't find it anymore.

    8 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 →
  4. SSRS 2016 Report Descriptions missing in report manager tiles

    In the new report manager which came SQL Server 2016 i'm missing the report description in the tiles.

    In our environment we used this field as a user friendly report name and the report name property as just a code. This way we could easily link to existing reports and never have to worry about changing report names, but without the descriptions the users won't know which report they must open.

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

    Upvotes: 8

    <=-=Oct 19 2016 4:13PM=-=>

    Thanks for your feedback Mark. A change for this is coming with SQL server 2016 SP1.

    -SSRS team

    <=-=Oct 19 2016 4:13PM=-=>

    Thanks for your feedback Mark. A change for this is coming with SQL server 2016 SP1.

    -SSRS team

    <=-=Jan 24 2017 3:17PM=-=>

    We have an SSRS 2016 SP1 Developer Edition instance running in native mode, and we still do not see descriptions on the report tiles.

    <=-=Aug 1 2017 1:39AM=-=>

    We are using SQL server 2016 SP CU3 and I don’t see any description on my reports, do you know if the change have been done ?

  5. Plain Text Password in Maintenance Plans

    The user and password of the user that create a Maintenance Plans using the MSSMS is save in plain text, you can use the following query to access this informaci�n.

    SELECT CAST(CAST(packagedata AS VARBINARY(max)) AS VARCHAR(max)) FROM sysssispackages
    WHERE name LIKE 'MaintenancePlansName'

    This will show the xml of Maintenance Plans including the user and password.

    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 →
  6. SSDT Clustered ColumnStore Rebuild Behaviour

    When adding a column to a table with a clustered column store index SSDT performs the following actions:
    1) Drop the CCS
    2) Adds the new column
    3) Adds a standard clustered index (non unique) on the first column
    4) Adds a clustered columnstore index using with DROP EXISTING ON

    It should just add the column - there is no need to drop and create the index twice.

    8 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 →
  7. SSMS 17.2 query window freezing

    Writing complex queries with databases containing a large number of objects causes SSMS to hang.

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

    Upvotes: 4

    <=-=Aug 22 2017 11:30AM=-=>

    Probably the same underlining issue, reported here:
    https://connect.microsoft.com/SQLServer/feedback/details/3035441/ssms-2016-freezes-locks-for-minutes-when-large-sql-code-block-is-commented-out
    https://connect.microsoft.com/SQLServer/Feedback/Details/776332
    I even created a video for Microsoft to see it, how it freezes and how CPU usage is high when it freezes, providing database, code and steps to reproduce and inviting them to collaborate with me to duplicate it, if they want, but to no avail. According to Microsoft, Jason, it is all just your imagination! :)

    <=-=Aug 22 2017 11:53AM=-=>

    I have had several co-workers try to reproduce the problem, it seems that older versions do not manifest this problem. I believe this bug was introduced recently.

    <=-=Aug 22 2017 12:02PM=-=>

    I have a dozen of databases (copies of each other, dev, test and so on) and they have approx. 8500 custom objects and when large code block gets commented and certain threshold is reached, my SSMS freezes for several minutes…so frustrating, and I…

  8. Integrate B2C AD with Azure SQL server

    Make it possible to integrate Azure B2C with Azure SQL server for Authentication and Authorizations

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

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Table variable declaration with non-existent sequence fails silently

    A batch containing a table variable that references a non-existent sequence fails silently and the remaining statements are ignored.

    This should produce the same error as for regular tables and temporary tables.

    DECLARE @T table 
    
    (
    id integer NOT NULL UNIQUE
    DEFAULT NEXT VALUE FOR dbo.NonExistentSequence,
    col1 integer NOT NULL PRIMARY KEY
    );

    INSERT @T (col1) VALUES (1);

    SELECT * FROM @T AS T;

    SELECT GETDATE();

    Commands completed successfully.

    Related: https://feedback.azure.com/forums/908035-sql-server/suggestions/34837312-improve-error-feedback-for-table-variable-declarat

    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. Microsoft SQL Server 2014: Incorrect result when selecting from nested query with UNION in CROSS APPLY

    When selecting from a nested query in an OUTER APPLY statement the nested query seems to be evaluated only once in certain circumstances.

    Test Case 1

    Evaluates nested FROM query for every row in VALUES (imho expected behaviour)

    SELECT

    v,
    
    v2

    FROM

    (VALUES (1), (2), (3), (4)) AS inner_query(v)
    
    OUTER APPLY (
    SELECT
    MAX(inner_v2) AS v2
    FROM (
    SELECT
    15 AS id,
    v AS inner_v2
    ) AS outer_query
    GROUP BY id
    ) AS outer_apply

    Result:

    | v | v2|
    |---|---|
    | 1 | 1 |
    | 2 | 2 |
    | 3 | 3 |
    | 4 | 4 | …

    7 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 →
  11. SQL server crashed (with dump) on this query (2017, latest CU)

    SQL server crashed on this query
    Query is attached
    Database can be found here (5Mb backup) https://gofile.io/?c=R8oJ1Q

    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 →
  12. TRY_PARSE and PARSE produce an error converting "NaN" value into Real or Float

    DECLARE @R REAL = TRY_PARSE('NaN' as REAL)
    SELECT @R
    GO

    DECLARE @F FLOAT = TRY_PARSE('NaN' as FLOAT)
    SELECT @F
    GO

    Both statements instead of NULL return an Error: "An error occurred while executing batch. Error message is: Arithmetic Overflow."

    Moreover, you can insert value in a table and any query, which will hit that value will fail with that error.

    DBCC CHECKDB recognizes it as a corruption.

    Seen on 2016 & 2019 on premise.

    7 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 →
  13. SQL Server 2019 scalar functions with inline are broken

    This SQL code returns "a" instead of "asdfg":

    CREATE FUNCTION [dbo].[GetPayload2] (@ID int) RETURNS VARCHAR(300) AS
    BEGIN
    IF @ID = 1
    RETURN 'asdfg'
    RETURN ''
    END
    GO
    SELECT dbo.GetPayload2(1)

    Reproduced on both 15.0.2000.5 and 15.0.2070.41. Works fine in SQL Server 2017.
    Workaround is to use WITH INLINE = OFF.

    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 →
  14. Can't create DACPAC of a SQL Server 2019 DB with External ODBC Datasources

    when trying to extract a DACPAC for a SQL Server 2019 database with external datasources that use the new ODBC functionality in Polybase you get the following error (this happens both in Visual Studio 2019 and SSMS 18.3.1):

    TITLE: Microsoft SQL Server Management Studio

    Could not extract package from specified database.
    Error 0: An error occurred while attempting to reverse engineer elements of type Microsoft.Data.Tools.Schema.Sql.SchemaModel.SqlExternalDataSource: Unsupported external data source type '6'.
    (Microsoft.SqlServer.Dac)


    ADDITIONAL INFORMATION:

    Unsupported external data source type '6'. (Microsoft.Data.Tools.Schema.Sql)


    BUTTONS:

    OK

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

    We’ll send you updates on this idea

    5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  15. Incorrect syntax error with CREATE EXTERNAL commands

    This applies to SQL 2019 RC1.

    First run this:
    exec sp_configure 'polybase enabled', 0
    reconfigure

    Then run this script:

    CREATE EXTERNAL DATA SOURCE MyAzureStorage

    WITH
    
    ( LOCATION = &#39;wasbs://<a rel="nofollow noreferrer" href="mailto:daily@logs.blob.core.windows.net">daily@logs.blob.core.windows.net</a>/&#39;
    , CREDENTIAL = AzureStorageCredential
    , TYPE = HADOOP
    )
    ;

    go
    CREATE EXTERNAL FILE FORMAT csvformat
    WITH (

    FORMAT_TYPE = DELIMITEDTEXT, 
    
    FORMAT_OPTIONS (
    FIELD_TERMINATOR = &#39;,&#39;
    )

    );
    go
    CREATE EXTERNAL TABLE [Avengers]
    (
            NAME nvarchar NOT NULL,
            LASTNAME nvarchar NULL,
            Email nvarchar NULL
    )
    WITH (DATA_SOURCE = PolyBaseDS)

    The output is:

    Msg 102, Level 15,…

    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 →
  16. Database Diagrams are crashing Microsoft SQL Server Management Studio 18.2

    After creating a new Databse Diagram, handling a modifed custom table view (maybe happening in other cases too) is impossible to reopen the diagram after closing the program without the Management Studio restarting.

    Is impossible to open the file, with the Management Studio aways restarting. Is getting very annoying to recreate the Diagram every time I need to use the Management Studio.

    No errors are shown, the program just restarts and never opens the Diagram.

    7 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 →
  17. CmdExec job step editor slow to open

    In SSMS 18.2, when trying to edit a CmdExec job step, the editor is super slow to open, often takes 30 or more seconds. This same behavior does not happen with T-SQL job steps.

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

    We’ll send you updates on this idea

    5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. SqlPackage.exe - CREATE USER [<name>] FOR EXTERNAL PROVIDER;

    CREATE USER [<name>] FROM EXTERNAL PROVIDER; is the correct syntax for creating database users from Azure AD.

    SqlPackage.exe generates CREATE USER [<name>] FOR EXTERNAL PROVIDER;. Executing this creates an invalid database user.

    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 →
  19. SSMS: Export of SSIS Project into ispac from Server doesn't wor

    when using the export function for an ssis project in SSMS 18.2 an error message comes up. The export fails and results in an an empty ispac file. Exporting the same project from the same server works with SSMS 17.9.1 but not with 18.2

    Info of SSMS which fails:
    SQL Server Management Studio 15.0.18142.0
    Microsoft Analysis Services Client Tools 15.0.1389.0
    Microsoft Data Access Components (MDAC) 10.0.14393.0
    Microsoft MSXML 3.0 4.0 6.0
    Microsoft Internet Explorer 9.11.14393.0
    Microsoft .NET Framework 4.0.30319.42000
    Operating System 10.0.14393

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

    Version of SSMS that succeeds:
    Microsoft SQL Server Management Studio 14.0.17289.0
    Microsoft Analysis Services Client Tools 14.0.1016.283 …

    7 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 →
  20. 18.2 Tabbing Bug Not Updating Query Window Text

    If I have multiple query tabs open at a time, switching between tabs causes a lag in actual displaying the content of the new tab.

    For example, if I have two tabs open with different queries on each tab. If I switch from one tab to another, the content doesn't appear to change in the query window, but if I highlight the text, then it'll change. This has been happening since the 18.0 GA release and I was hoping subsequent updates would fix it, but they have not. I have attached three files.

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

SQL Server

Categories

Feedback and Knowledge Base