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. Query store create database

    If you enable Query Store on model, then attempt to create a database, Query Store will be enabled on the new database.

    However, if you attempt to create a database using a non-default collation, the CREATE database fails with a deadlock on sys.sysschobj, in the middle of a DQS transaction. (I'm using 2017 CU4)

    I should be able to specify a non-default collation when creating a database, and not have DQS cause a failure.

    --Enable Query Store on model
    ALTER DATABASE model SET QUERYSTORE (OPERATIONMODE = READWRITE);
    GO
    --Create a database using any collation other than your

    16 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. xp_delete_file on SQL Server 2017/Linux

    The xpdeletefile system stored procedure for deleting bakup file does not work on Linux client OS.
    Wee tested on Microsoft SQL Server 2017 (RTM-CU1) (KB4038634) - 14.0.3006.16 (X64) Enterprise Edition (64-bit) on Linux (Ubuntu 16.04.3 LTS)

    Script we used :
    DECLARE @BACKUPDIR NVARCHAR(256);

    EXEC master.dbo.xp
    instanceregread
    @rootkey = 'HKEY
    LOCALMACHINE',

    @key = 'Software\Microsoft\MSSQLServer\MSSQLServer',

    @value
    name = 'BackupDirectory',
    @BackupDirectory = @BACKUPDIR OUTPUT;
    SELECT @BACKUP
    DIR

    EXEC master.sys.xpdeletefile 0, @BACKUP_DIR, N'bak', N'21111111';
    GO

    Error message :
    Msg 22049, Niveau 15, État 0, Ligne 67
    Error executing extended stored procedure: Invalid Parameter

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  3. service broker target not functional on extended events

    I filed a question on StackOverflow, if SQL Server 2017 supports a service broker service as a target for extended events. It seems to be configurable, but no events are written to the service broker queue.

    Any ideas?

    https://dba.stackexchange.com/questions/196571/is-there-a-service-broker-target-for-an-extended-event-session

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

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. SSDT 17.2 for VS 2015 - SSIS 2016 packages can't open Analysis Services Processing tasks

    I upgraded an SSIS project from 2014 to 2016 using SSDT 14.0.61707.300 in Visual Studio 2015. Upon doing so, whenever I open a Analysis Services Processing Task, I get the following error:

    TITLE: Analysis Services Processing Task

    Method not found: 'Microsoft.AnalysisServices.ErrorConfiguration Microsoft.AnalysisServices.Commands.BatchCommand.get_ErrorConfiguration()'.

    If I revert back down to 2014, I can open it just fine. If I create a new AS Processing Task in the same package or new package in the same solution, I get the same error. If I upgrade the SSIS project to SQL2017, it magically works. The issue is only when the target version is 2016.…

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

    Upvotes: 13

    <=-=Dec 4 2017 3:53AM=-=>

    Hi Gabe,
    I’m having a similar problem, but not only with upgraded packages.
    I’m having problems also if I create a completely new package
    with Integration Services 2016 in Visual Studio 2015 (SDDT version installed is 17.2).
    It works if I use Integration Services 2014 or 2017.

    I’ve not yet found solution to that issue.

    Please let me know if you identify a solution to your issue

  5. Enable SSIS Double Hop authentication to work with Windows Defender Credential Guard

    Windows Defender Credential Guard enabled machines only allow Kerberos Constrained delegation. SSIS double hop authentication will not work with either full delegation or constrained delegation once Credential Guard is enabled. Connecting to an Integration Services catalog server and executing a package from a Credential Guard enabled client will fail with “NT AUTHORITY\ANONYMOUS LOGON”.

    Enabling SSIS to work with constrained delegation is imperative for us since the Credential Guard security feature is enabled in our environment and I am certain that many out there are dealing with the same issue.

    15 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 →
  6. save passwords v18

    SSMS v18.0 doesn't save password properly for each server. Save the password from one server, then attempt to connect to another server with a save password and it will fail. Using SQL authentication and version 15.0.18118.0 and migrated my settings from SSMS v17.9.1.

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

    We’ll send you updates on this idea

    9 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  7. DBCC CHECKDB needs to check the checksums on In-Memory OLTP (Hekaton) tables

    Today (SQL 2014 & 2016), CHECKDB skips in-memory OLTP tables. It needs to check the checksums on those tables so that we can find corruption before we find it the hard way.

    Scenario: weekly full backups on Saturday, and log backups every X minutes. Corruption strikes on Monday, and we find out when we have an accidental reboot on Friday. The database is now completely down, and we have to wait until we restore the database from full + all transaction logs since.

    15 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 →
  8. Databases not accessible by default on auto-unlocked BitLocker drive

    Take the following BitLocker set up:

    C:\ OS Drive (encrypted) - Windows and SQL Server installed here
    D:\ Database Drive (encryped + auto-unlock)

    When Windows boots, it seems that the MS SQL Server service starts before BitLocker auto-unlocks the drives. Therefore, when SSMS is started, the databases are inaccessible (labelled as Recovery Pending). Also, any attempt to access the database data in SSMS results in strange read/write error dialogs:


    Msg 823, Level 24, State 2, Line 1

    The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x000000005f4000 in file 'D:\Databases\MyDb_Data.mdf'. Additional

    15 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 →
  9. SSMS 17.1 Add New Firewall Rule Error Code 401: Add IP when logging into Azure DB for the first time.

    The title says it all.
    New SSMS install on new PC, to new DB on new Azure SQL Server.� Prompted to Log in to Azure, OK.
    'New Firewall Rule' dialog Prompts to add firewall rule to Azure, OK. Click OK and get error
    "An error occurred while creating a new firewall rults (HTTP Status Code 401)) (ConnectionDlg)"

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

    We’ll send you updates on this idea

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

    Sorry folks, but we are not able to repro this issue (either using SSMS 17.9.1 or SSMS 18 Preview 7).

    Since multiple people out there are reporting this issue, it is obvious that we are missing something that is specific to your environment or configuration.

    Could you help us out and try to describe a little better your subscription/environment/account/permissions?

    For example, does the following mainstream scenario works for you all:
    1) Connect to Azure Portal
    2) Create SQL server+database
    3) Go to SSMS and connect to
    4) Add firewall rule

    If it does, then can you identify what is different between the case where it works and the case where it does not?

    Thanks,
    -Matteo

  10. "[DbId:XX] ADR enabled for the database." logged all the time in ErrorLog

    Hi Team,

    We were testing ADR in a two SQL Server 2019 CU 4 Developer Edition servers, with a AG setup. After enabling ADR for every database in those instances, the secondary server started to log this message "[DbId:XX] ADR enabled for the database." in the ErrorLog every few seconds for a given database if there was a transaction in that database in the primary server within those seconds.

    Ie. We have queries constantly reaching db ids 14 and 40, so we see that message constantly in the secondary for those db ids. For the dbid 16, I just created…

    13 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 →
  11. SSMS 18 Remembers password for user, not specific to database

    I have a number of SQL Server connections which use the same login but each has a different password. Before SSMS 18 the remember password function worked correctly, storing the password for individual connections.

    Under SSMS 18 it appears to only be storing the last used password for the login regardless of the server connection.

    Can this be restored to the previous functionality.

    13 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 →
  12. Self referencing scalar function nesting level exceeded when adding a select

    Bug report on Self referencing scalar functions following this question, answered by Paul White here:

    https://dba.stackexchange.com/questions/239324/self-referencing-scalar-function-nesting-level-exceeded-when-adding-a-select

    In short a self referencing scalar function's references are evaluated when it should not be, resulting in an infinite loop in certain circumstances.

    Reproducing the issue:

    CREATE FUNCTION dbo.test6(@i int)
    RETURNS INT
    AS
    BEGIN
    RETURN(
    SELECT TOP 1
    CASE
    WHEN @i = 1 THEN 1
    WHEN @i = 2 THEN 2
    WHEN @i = 3 THEN (SELECT dbo.test6(1) + dbo.test6(2))
    END
    )END;

    SELECT dbo.test6(3);

    Resulting in the error:
    Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32).

    Part of the answer…

    13 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 →
  13. filegroup to read_only prevents dbcc checkdb from running

    My database uses a combination of partitions and file groups in a sliding window configuration. I have implemented the VLDB CheckDB pattern and found that all file groups must be in a read-write state for this to work. By placing some older file groups into a read-only state I was hoping to utilize partial backups to reduce backup times. As a workaround we are temporarily placing the file groups back into a readwrite state to allow the checks to continue - however to make sure our FG backups can be used in a restore the FG backups have to be…

    13 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 →
  14. LAST_MODE should map to LCK_M_RX_X in the lock_mode Extended Event

    This is just plain wrong.

    SELECT mv.name, mv.mapvalue, xo.description, xp.description
    FROM sys.dm
    xemapvalues AS mv
    JOIN sys.dmxeobjects AS xo

    ON  mv.object_package_guid = xo.package_guid
    
    AND mv.name = xo.name

    JOIN sys.dmxepackages AS xp

    ON xo.package_guid = xp.guid
    

    WHERE mv.name = 'lockmode'
    ORDER BY mv.map
    key;

    13 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 →
  15. SQL SERVER 2016 (SP2-CUI) BUG? MERGE and INSERT with COLUMNSTORE index creates crash dump - script supplied

    Hi

    I have managed to create a script that (on my system) reliably generates the following message

    Location: pageref.cpp:955
    Expression: ISOFF (BUFMINLOGGED, mbuf->bstat) || pageModifyType != PageModifyTypeContents || GetPagePtr ()->IsTextPage ()
    SPID: 59
    Process ID: 5080
    Msg 3624, Level 20, State 1, Line 45
    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent…

    13 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 →
  16. MDS Explorer should show Attribute description of Name and Code attributes.

    It's possible to set Attribute description on system attributes Name and Code in the same way as user defined attributes on an entity in MDS. But Description only shows in MDS Explorer for user defined attributes not for Name and Code. I expected this to work the same way for system and user defined attributes.

    SQL Server version 13.0.4466.4
    MDS Schema version 13.1.0.3

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. SSDT error SQL46010 on iif

    SSDT reports an error on this valid syntax:

    create procedure test
    as

    if (iif(1 = 1, 1, 0)
    
    )
    &lt; 2
    select &#39;ok&#39;

    Severity Code Description Project File Line Suppression State
    Error SQL46010: Incorrect syntax near ). Stored Procedures\Procs2\test.sql 4

    See https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8ec0a584-1eec-4ffb-b5b2-1df6092817e6/sql46010-incorrect-syntax-near-?forum=ssdt

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. SSRS Bug: Choose new target for linked report offers no reports

    Install and configure SQL Server Reporting Services 2016SP1CU7 (mine was a Migration from 2008R2SP3, but an empty one should do). Upload a 'master' Report and create a link to it. Delete the 'master' and re-upload it. The link is now orphaned as expected.

    In previous Versions, one could re-map the link to a different master without losing parameter configuration. It had problems with hidden folders, but allowed to enter a path explicitly by hand.

    2016 pops up a selector box (aggravatingly using tiles no matter how often I dell it I want lists), which allows browsing folders, but all folders…

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

    We’ll send you updates on this idea

    under review  ·  4 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  19. SSDT (14.0.61709.290) Unable execute SSIS package on server that contains a script component.

    When using Visual Studio 2015 (14.0.25431.01) and the latest version of SSDT (14.0.61709.290) on my client machine we are no longer able to execute a SSIS packages from the SSISDB in SQL Server 2016 (13.0.4451.0) on the server machine when it contains a script component and the single package is deployed. I have made sure project TargetServerVersion is SQL Server 2016.

    When we try to execute the package from the server we get the following errors.

    The component is missing, not registered, not upgradeable, or missing required interfaces.

    Script failed validation and returned error code 0xC0048021

    The component metadata for…

    13 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 →
  20. Partition Table using min/max functions and Top N - Index selection and performance

    Partitioned Tables performance issues - For select statements using Min and Max functions and Top N with ordering over an index.

    Poor performance is being detected for Queries on partitioned tables utilising the min and max functions and select Top N clause with "order by" matching columns of the index.

    The candidate index is either not being used or is being used to scan or seek all rows rather than a subset.

    13 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: 125

    <=-=Aug 10 2007 9:17PM=-=>

    Hi Microsoft, please confirm this optimizer problem by running the scripts, it is self evident and can be optimised significantly better.

    Eg. For a minimum, the optimal plan is to obtain the minimum for each partition using the index and then taking the minimum of all the (partition) results. The same principle can apply to maximum, and for Top N over an index …

    The plan should stand out as optimal, because the number of reads over the index is very small, and there will be one set of page reads (usually only one page) for each partition…. you can use the assumption that the number of partitions is significantly smaller than the number of rows (or even count the number of partitions), to estimate the cost (page reads) – which comes out at about N pages where N is the number of partitions.…

  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base