SQL Server

Microsoft SQL Server 2017 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 2017 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. 1 vote
    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 →
  2. sys.time_zone_info shows incorrect values for current_utc_offset and is_currently_dst for GMT Standard Time

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

    Returns +01:00 and 1, respectively, for current_utc_offset and is_currently_dst, 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), but may impact other SQL versions…

    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 →
  3. SSMS v18.2 inserts object name to query window when changing object name in Object Explorer

    Steps to reproduce:
    In Management Studio change a view name (can be any object) directly in Object Explorer and click on another view to remove the focus.
    On the confirmation window answer Yes.
    As soon as you click Yes, SSMS will insert the 2nd view's name in your query window.
    If you are not aware of this bug, it can alter your code you are currently working on.

    1 vote
    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 →
  4. Recursive CTE breaks SQL Server service

    Query below crashes SQL Server service. Tested on SQL Server 2017 Developer Edition CU16.

    ;with cte_recursive as
    (
    select
    convert(char(8000), '') column1
    ,convert(char(79), '') column2
    union all
    select
    convert(char(8000), '') column1
    ,convert(char(79), '') column2
    from cte_recursive
    )

    select *
    from cte_recursive

    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 →
  5. function inlining

    In SQL Server 2019 function is marked as inlineable but it's not and query comes back with following error:

    Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.

    Looks like SQL Server 2019 doesn't properly identify if function is inlineable and throws error vs just not inline it.

    1 vote
    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. SSMS 18.3 create distributed ag syntax error works in 17.9.1

    Running the code below ( from https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/configure-distributed-availability-groups?view=sql-server-2016):

    ALTER AVAILABILITY GROUP [distributedag]
    JOIN
    AVAILABILITY GROUP ON
    'ag1' WITH
    (
    LISTENER_URL = 'tcp://ag1-listener.contoso.com:5022',
    AVAILABILITY_MODE = ASYNCHRONOUS_COMMIT,
    FAILOVER_MODE = MANUAL,
    SEEDING_MODE = AUTOMATIC
    ),
    'ag2' WITH
    (
    LISTENER_URL = 'tcp://ag2-listener.contoso.com:5022',
    AVAILABILITY_MODE = ASYNCHRONOUS_COMMIT,
    FAILOVER_MODE = MANUAL,
    SEEDING_MODE = AUTOMATIC
    );
    GO

    returns an error in SSMS 18.3

    "Incorrect syntax near DISTRIBUTED"

    Works in 17.9.1

    1 vote
    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 →
  7. SQL Server Management Studio - Blank Windows

    When I bring up a new query window inside SQL Server Management Studio other windows that I have up go blank. This forces me to close and re-open Management Studio in order to continue working. Can you please fix this?

    Version Info:
    SQL Server Management Studio 15.0.18131.0
    Microsoft Analysis Services Client Tools 15.0.1347.0
    Microsoft Data Access Components (MDAC) 10.0.18362.1
    Microsoft MSXML 3.0 6.0
    Microsoft Internet Explorer 9.11.18362.0
    Microsoft .NET Framework 4.0.30319.42000
    Operating System 10.0.18362

    1 vote
    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. Fix SSMS open diagram crash

    1) Create diagram
    2) Close SSMS
    3) Open SSMS
    4) Open diagram
    5) SSMS silence crash

    1 vote
    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. 1 vote
    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. express sql express 2019 ubuntu This is an evaluation version. There are [139] days left in the evaluation period.

    I setup SQL Express 2019 on Ubuntu but getting this warning:

    This is an evaluation version. There are [139] days left in the evaluation period.

    1 vote
    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.3 - unable to change event from lookup (Extended Events)

    The attached file show the problem with lookup for changing event in the Extended Events Session on SSMS 18.3. The lookup shows just for a moment and in the improper place.

    It is Windows 1903 with most recent updates.

    1 vote
    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. An SQL script parsing error

    Execute the following SQL script:
    --
    create table tableA(
    id int,
    name varchar(20)
    )

    create table tableB(
    age int,
    *** int
    )

    insert into tableA values (1,'a'),(2,'b'),(3,'c')

    insert into tableB values (20,0),(30,1),(40,0)
    --

    and then execute this:

    --
    select * from tableA where id in (select id from tableB)
    --

    You will find a surprising result.
    tableB does not have a cloumn named id,but this script worked normal.

    and it works like
    --
    select * from tableA where id = id
    --

    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 →
  13. Data Model Designer Custom View Modifications Crash SSMS

    I am using SSMS 18.3, but the same problem has persisted through SSMS 17.8-18.3. The data model designer is consistently crashing when I am adding or removing attributes from the custom model view. I am using SSMS to design data models for a project I am working on, and this defect is a major problem and has been a daily setback . I read another thread here that says you're working on old code, but this functionality only broke recently. Please fix this ASAP.

    SQL Server Management Studio 15.0.18178.0
    Microsoft Analysis Services Client Tools 15.0.1487.0
    Microsoft Data Access Components (MDAC)…

    1 vote
    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. Data Model Designer Custom View Modifications Crash SSMS

    I am using SSMS 18.3, but the same problem has persisted through SSMS 17.8-18.3. The data model designer is consistently crashing when I am adding or removing attributes from the custom model view. I am using SSMS to design data models for a project I am working on, and this defect is a major problem and has been a daily setback . I read another thread here that says you're working on old code, but this functionality only broke recently. Please fix this ASAP.

    SQL Server Management Studio 15.0.18178.0
    Microsoft Analysis Services Client Tools 15.0.1487.0
    Microsoft Data Access Components (MDAC)…

    1 vote
    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. stop VS from trying to automatically upgrade SSIS solutions if the version of VS you open does not have SSIS addon installed

    stop VS from trying to automatically upgrade SSIS solutions if the version of VS you open does not have SSIS addon installed or does not support the version of SSIS packages in the project. This is annoying and in some cases forces me to revert to a backup of my project. I have multiple versions of VS installed. If I open a SSIS project in the latest VS by accident (or version selector opens it in the wrong version), and that VS does not yet have SSIS components installed, it should not mess with the project at all. This is…

    1 vote
    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. Invaild Urn filter exception on Script View as and other functions

    After having SSMS running for a few hours, the script objects functionality will stop working in version 17 and higher. This occurs when going to a view and right-clicking and selecting script view as and picking any of the options. Usually, you have to use the application for a while before this starts to happen, but when it starts, you have to restart SSMS to correct it. Below are the error details and stack trace.

    Attempt to retrieve data for object failed for Server 'xxxxxdev.org'. (Microsoft.SqlServer.Smo)

    ------------------------------
    For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=15.0.18178.0+((SSMS_Rel).190920-0145)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attempt+to+retrieve+data+for+object+Server&LinkId=20476

    ------------------------------
    Program Location:

    at Microsoft.SqlServer.Management.Smo.Server.GetSmoObject(Urn urn)
    at Microsoft.SqlServer.Management.Smo.CreatingObjectDictionary.SmoObjectFromUrn(Urn urn) …

    1 vote
    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 →
  17. Microsoft.SqlServer.TransactSql.ScriptDom.TSqlParser fails parsing simple valid expression

    There appear to be a bug in Microsoft.SqlServer.TransactSql.ScriptDom

    Here is a c# snippet:

    using Microsoft.SqlServer.TransactSql.ScriptDom;

    var parser = new TSql150Parser(true);

    string expr = @"IIF( (IIF(1 = 1, 1, NULL)) IS NULL, 1, 0)";

    var res = parser.ParseExpression(new StringReader(expr), out var errors);

    bool isSuccess = errors.Count == 0;

    Actual result: isSuccess is false
    Expected result: isSuccess is true

    3 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 →
  18. BUG with

    I have found a bug related to calling stored procedure with parameters. If one, by mistake, omits "@" in parameter name the compiler doesn't complain- but rather takes the parameter name and implicitly converts it into a string.
    We end up with a bug that is really difficult to discover.
    This has been tested on SQL2014 and SQO2017.

    1 vote
    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. BUG with

    I have found a bug related to calling stored procedure with parameters. If one, by mistake, omits "@" in parameter name the compiler doesn't complain- but rather takes the parameter name and implicitly converts it into a string.
    We end up with a bug that is really difficult to discover.
    This has been tested on SQL2014 and SQO2017.

    1 vote
    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. Why does Find and Replace in SSMS 18.2 default to "All Open Documents"?!

    Why on earth does Find and Replace default to "All Open Documents"?!

    You don't know how many times I have replaced things in other query windows unintentionally. If I am fortunate, I catch it and do Ctrl-Z to undo it.

    Just now I did a replace, and SSMS froze while it happily did a replace in all the query windows I had open , to the tune of 63,514 replacements!

    A much more sensible default would be "Current Document". Or better yet, allow the default to be set under Tools... Options...

    Please change this.

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

SQL Server

Categories

Feedback and Knowledge Base