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. OPENROWSET T-SQL and MOLAP provider fail on complex DAX statements

    Running the OpenRowSet (SQL2016) against a SSAS 2017 on-premise or Azure SSAS will fail with error

    OLE DB provider "MSOLAP" for linked server "(null)" returned message "OLE DB error: OLE DB or ODBC error: An unexpected exception occurred.."

    T-SQL Statement:

    SELECT *
    FROM OpenRowset('MSOLAP','DATASOURCE=<Servername>;Initial Catalog=<cube>;User ID=<userid>;Password=<password>’,
    '<DAX STATEMENT>’)

    Running the DAX directly against SSAS (2017) returns the correct results, also the OpenRowSet command works fine in SSAS 2016 using the same DAX statement.

    Bug maybe due to the properties differences in the OpenRowSet implementation rather than the MOLAP provider (these are the XML properties included in the MDX query to…

    38 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 →
  2. SSIS package fails to start - application lock timeout in SSISDB.catalog.create_execution

    Details are described here:
    https://connect.microsoft.com/SQLServer/feedback/details/783291/ssis-package-fails-to-start-application-lock-timeout-in-ssisdb-catalog-create-execution

    In short: when a scheduled job tries to execute an SSIS package , there's a time-out in the communication between the job and the SSISDB database. The package is never executed. The original bug reports was closed as duplicate (no duplicate to be found though).

    I encountered this bug in SQL Server 2017, patched to the latest CU.

    Error message: Failed to execute IS server package because of error 0x80131904. Description: The operation failed because the execution timed out. Source: .Net SqlClient Data

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

    We’ll send you updates on this idea

    under review  ·  10 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. SSMS screen is not correctly redrawn when switching tabs

    Sometimes when switching between tabs in SSMS the screen is not correctly refreshed (redrawn).
    The result is a corrupt screen partly showing the previous tab contents and partly showing the newly active tab contents.
    In particular this happens when using "Database Diagrams" tabs.

    This has been a permanent bug through a number of the latest SSMS releases including this release:
    Release 16.5.1
    File version: 13.0.16100.1

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

    We’ll send you updates on this idea

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

    Upvotes: 6

    <=-=Dec 12 2016 1:42AM=-=>

    This has been reported more times than you have used SSMS. MS are too incompetent and lazy to fix it.

    <=-=Dec 12 2016 1:46AM=-=>

    Here is the link to another which also has a link to another report

    https://connect.microsoft.com/SQLServer/Feedback/Details/3109897

    please click on the I CAN TOO in the repros section

    <=-=Dec 21 2016 7:39AM=-=>

    I can replicate this on multiple different computers, each with freshly installed Windows (either 8.1 or 10) and latest of all drivers. It happens both with Intel integrated graphics (for me is HD 4600) and NVidia cards. It’s clearly a bug in how you’re using the Visual Studio shell.

    This is absolutely HORRIBLE!! When closing a tab, then attempting to execute the query in a tab that was already open and is now focused (because you just closed one), you see the wrong text in the tab, and…

  4. Update produces impossible result

    The following produces an illogical result:

    DECLARE @Target table
    (

    c1 integer PRIMARY KEY, 
    
    c2 integer NOT NULL,
    c3 integer NOT NULL

    );

    DECLARE @Source table
    (

    c1 integer NULL, 
    
    c2 integer NULL,
    c3 integer NULL,

    INDEX c CLUSTERED (c1)

    );

    INSERT @Target

    (c1, c2, c3) 
    

    VALUES

    (1, 0, 0);
    

    INSERT @Source

    (c1, c2, c3) 
    

    VALUES

    (1, 2, NULL),
    
    (1, NULL, 3),
    (1, 4, 4);

    UPDATE T
    SET T.c2 = S.c2,

    T.c3 = S.c3
    

    FROM @Target AS T
    JOIN @Source AS S

    ON S.c1 = T.c1;
    

    SELECT * FROM @Target AS T;

    Result:

    c1 c2 c3
    1 2 3

    The…

    33 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 →
  5. Identical symmetric keys do not work between SQL Server 2017 and other SQL Server version

    hi everybody!

    I believe, there is a general product issue in SQL Server 2017. The problem concerns encrypting & decrypting data using the same symmetric key on different servers.
    I have an issue in SQL Server 2017 CU3 (version 14.0.3015.40). I need to create identical symmetric keys on two servers of different versions, as it is described in MS article:

    https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/create-identical-symmetric-keys-on-two-servers

    These steps work well within and between different versions of SQL Servers (2012, 2014, 2016), but not between SQL Server 2017 and any other server.
    I can create identical symmetric keys on SQL Server 2012, 2014 and 2016. So…

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

    We’ll send you updates on this idea

    under review  ·  12 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. Key Lookup against Columnstore Index Causes Slow Query Execution

    On tables with a clustered columnstore index and a b-tree index on the same table, some parameter sets get an execution plan with an index seek against the b-tree, and then key lookup (in row mode) against the columnstore. This is extremely expensive, and most of the queries against larger columnstores never complete. The remedy is to hint the columnstore index in the query. I can supply plans as needed, but apparently can't upload here.

    31 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 →
  7. SQL 2017 CU7 - using In-Memory OLTP table variable inside MSTF causes error

    The code from attached file causes error as:
    Msg 3628, Level 16, State 1, Line 39
    The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator.

    31 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 →
  8. SSIS 2016 packages abort with �Unexpected Termination� message

    We have a straight forward implementation in deploying the SSIS 2016 packages (migrated from SSIS 2008 R2) onto the SSISDB and then calling these packages through a SQL Agent job.
    The job calls the parent wrapper package and this in turn will call the necessary child packages based of the files that has to be loaded.

    However, when we execute the same package multiple times, the execution of the child package fails with the status �Unexpected Termination�.
    We do not find any error messages within the Execution reports of the SSIS package. This issue will be resolved once we redeploy…

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

    We’ll send you updates on this idea

    7 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. Reordering an XML column

    Reordering an XML column in SQL server management studio's results grid affects the "View XML" feature.
    Clicking on a cell of an XML column shows wrong data.

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

    Upvotes: 0

    <=-=May 2 2011 8:50AM=-=>

    Hi DamiLaufer
    Thanks for taking the time to report this issue. We have investigated and found this is a known bug that has not made it to the top of our list yet. I’m resolving this item for now, but do have a work item tracking it.

    Thanks,
    -Sam Hughes

  10. SQLLocalDB Utility 2016 returns "FormatMessageW failed. Error code returned: 15100"

    A recent update to SQL Server Express LocalDB 2016 causes errors when attempting to display output for several options while using the sqllocaldb.exe command-line utility.

    I current have Microsoft SQL Server 2016 (version 13.0.5026.0) installed (only LocalDB). "SELECT @@VERSION;" displays:

    Microsoft SQL Server 2016 (SP2-CU3) (KB4458871) - 13.0.5216.0 (X64)

    When executing the following program:

    "C:\Program Files\Microsoft SQL Server\130\Tools\Binn\SqlLocalDB.exe"

    the following options get the stated errors:

    -? as well as any invalid option receives:
    FormatMessageW failed. Error code returned: 15100

    i {invalidinstancename} receives:
    FormatMessageW failed. Error code returned: 15100
    FormatMessageW failed. Error code returned: 15105

    i {validinstancename}…

    28 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 →
  11. SEQUENCE gets reset on Publish from SSDT DB Project

    When you add a sequence to a database project and have it start at 1 and then deploy the project to a database, the first time it gets created correctly.
    When you get more values and the sequence next value is 100 and then publish the project again, the publish generates an ALTER SEQUENCE dbo.SequencObject RESTART WITH 1; statement and that should not happen when the sequence object already exists.

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

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. SSDT 17.x - Unable to preview SSIS OLE DB Data Source when using Oracle Connector

    I have an SSIS packages that queries an Oracle data source. When trying to preview the query in the data source configuration window, it errors out.

    Technical Details:
    Visual Studio 2015, Update 3, Version 14.0.25431.01
    SSDT 17.4 (Build 14.0.61712.050)
    Oracle Client 12.1.0
    OLE DB Connector: Oracle Provider for OLE DB

    Error Details:

    There was an error displaying the preview. (Microsoft Visual Studio)

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

    The system cannot find message text for message number 0x80040e51 in the message file for OraOLEDB. (OraOLEDB)


    Program Location:

    at Microsoft.DataTransformationServices.Design.UnsafeNativeMethods.ICommandWithParameters.GetParameterInfo(IntPtr& pcParams, IntPtr& prgParamInfo, IntPtr& ppNamesBuffer)
    at Microsoft.DataTransformationServices.Design.DesignUtils.GetQueryParameters(ConnectionManager connectionManager, String sqlStatement)
    at Microsoft.DataTransformationServices.Design.PipelineUtils.ShowDataPreview(String sqlStatement, QueryParameter[] parameters, ConnectionManager…

    27 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 →
  13. SSMS - Right-click menu option to "Design" tables configured as Temporal Tables is missing

    I am using the new Temporal Table feature on certain tables in my database.

    When I navigate to such tables via SSMS Object Explorer, I have found that the "Design" right-click menu option is not present for Temporal Tables. (Or as SSMS labels them, "System-Versioned" tables.)

    The "Design" option is, however, still available for NON-temporal tables.

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

    We’ll send you updates on this idea

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

    Upvotes: 0

    <=-=Mar 7 2017 2:10AM=-=>

    Thank you for taking time to post this issue!
    I can confirm that Design option in SSMS Object Explorer is not available for temporal (system-versioned) tables.
    Unfortunately, we do not plan to include a fix for this issue in the upcoming release.
    We might include it as an improvement in a future release, though.
    How important for you is to have this option available for temporal tables?

  14. CDW from 2016 to 2017 ends with "Property HasMemoryOptimizedObjects is not available for Database"

    Hi
    I'm trying to copy a couple of databases from a SQL2016 to SQL2017 using the Copy Database Wizard.
    I'm using SQL Management Object Method in SSMS 17.3
    SSIS Proxy account is sysadmin on both instances and local admin i Windows on both servers.
    When running the job I get the error "Property HasMemoryOptimizedObjects is not available for Database '[DATABASENAME]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights.
    The databases has no Memory Optimization configured.

    If I try to use detach/attache methods I can't select any of the databases witch…

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

    We’ll send you updates on this idea

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

    25 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 →
  16. MERGE not working when index created on temporal table.

    Following are the steps to reproduce the MERGE statement issue in any SQL 2017 database.
    Script is attached for all the steps.

    --Steps to reproduce fail Scenario


    1. Create table in SQL Server 2017 database with named system versioned temporal/history table.

    2. Create non-clustered index on the temporal/history table.

    3. Insert 400+ records in table.

    4. Execute the merge statement (source table should have data for both Insert and Update scenario), and it will fail with following error

    Msg 681, Level 16, State 3, Line 453
    Attempting to set a non-NULL-able column's value to NULL.

    --Steps to see success scenario


    1. Drop the index from…
    25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Fix the Problem of Converting Hijri Dates to Gregorian Dates

    Currently Microsoft tsql function called Convert() is not able to convert the Hijri date 'yyyy-02-30' to its corresponding Gregorian Date, here are the details of this issue

    https://social.msdn.microsoft.com/Forums/en-US/b86b0cf6-280d-436e-ba92-ff168794c420/error-in-converting-hijri-date-to-gregorian-date?forum=sqlnetfx&prof=required

    25 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 →
  18. Cannot script external table in SSMS 18.2

    I receive the error message attached when trying to script an external table in SQL Azure in SSMS 18.2.

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

    We’ll send you updates on this idea

    started  ·  19 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. Error when connecting to SSAS via msmdpump.dll in SSMS 18.5

    Hi,

    We have an SSAS instance with https access configured via msmdpump.dll. In 18.4 connection works fine, but in 18.5 it gives following error:

    Cannot connect to https://myserver/OLAP/msmdpump.dll.


    ADDITIONAL INFORMATION:

    String reference not set to an instance of a String.
    Parameter name: s (mscorlib)


    Could you check what is the reason?

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

    We’ll send you updates on this idea

    7 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. Traceflag 460 causing truncation errors on code paths that are not followed

    This is an odd one. I have tested this on both SQL Server 2017 CU12 and CU13 (in a container and on my production boxes).

    If you have an IF/ELSE condition, and you are inserting into a table variable in the ELSE, and that INSERT would cause a truncation issue, it will throw an error, EVEN IF THE CODE IS NOT EXECUTED.

    I have attached a reprop script that creates a database called "Repro" and runs the code. When TF460 is enabled, the ELSE block with throw an error when inserting into a table variable, even though it is impossible…

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

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base