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. SSMS 18.1 Crashes when Opening a Database Diagram

    SSMS 18.1 crashes (and restarts) when opening a database diagram without any error message.

    I have created several diagrams from scratch thinking it might have to do with old formatting, but this does not appear to be the case.

    You can edit a diagram (adding dozens of tables) with no problem. It is the opening of the diagram that results in the crash.

    Latest bits for SSMS and SQL Server 2017 installed today.

    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…

    1,190 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    648 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  2. Porting SMO Library to .NET Core

    SQL Server has been ported to Linux for over a year now and it is time the complete SMO library (or what can be) is ported over to cross-platform as well.

    Only 9 or so core files have been ported over to .NET Core and this allowed the sqlserver module to port over a small set of cmdlets to PS Core. This does not work for other modules like dbatools that use a wider berth of the library.

    There are plenty of other modules in PowerShell (and applications too) that would like to provide cross-platform support for managing SQL Server…

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

    We’ll send you updates on this idea

    4 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

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

    We’ll send you updates on this idea

    started  ·  17 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  4. SSMS 18.4 SQLServer 2019 CU2 Object explorer fails for SQLAgent

    After applicting CU2 on SQLServer 2019, SSMS18.4 fails to show SQLAgent jobs via object browser.

    TITLE: Microsoft SQL Server Management Studio

    Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

    For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476


    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)


    A severe error occurred on the current command. The results, if any, should be discarded. (Microsoft SQL Server, Error: 0)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=15.00.4013&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476


    BUTTONS:

    OK

    19 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 →
  5. SSMS 18.0 unable to export Extended Events XEL to XEL

    SSMS 18.0 is unable to export an Extended Events XEL file to another XEL file.

    When viewing an XEL file in SSMS, using the Extended Events menu command "Export to" > "XEL file..." results in this error:

    (Error Summary)

    TITLE: Microsoft SQL Server Management Studio

    Method not found: 'Void System.Object.SerializeEvent(Microsoft.SqlServer.XEvent.Linq.IEventSerializer, Microsoft.SqlServer.XEvent.IMetadataGeneration)'. (Microsoft.SqlServer.XEvent.Linq)

    BUTTONS:

    OK

    (Error Detail)

    Method not found: 'Void System.Object.SerializeEvent(Microsoft.SqlServer.XEvent.Linq.IEventSerializer, Microsoft.SqlServer.XEvent.IMetadataGeneration)'. (Microsoft.SqlServer.XEvent.Linq)

    Program Location:
    at Microsoft.SqlServer.XEvent.Linq.XEventFileProvider`1.SerializeEvent(IEventSerializer serializationContext, TEvent serializableEvent)
    at Microsoft.SqlServer.XEventStorage.ComputedGridStorage.SaveData(Object param)

    I reported this same issue for a previous version of SSMS (17.?) via connect item 3136373 on 2017-06-22 and it was fixed in a later minor update…

    15 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 →
  6. SSMS 17.2 (and 17.1) Mirror configuration fails because mirror database is restoring

    Attempting to configure database mirroring through the SSMS 17.2 (and 17.1) GUI between two SQL 2016 servers fails with "Database 'Test' cannot be opened. It is in the middle of a restore."

    15 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. Too Many Decimal-places in Size (MB) property

    The "Size (MB)" property in SSMS reports the size with way too many decimal places if the size is not divisible by 1024. This can make quickly understanding the sizes of your databases in Object Explorer Details frustrating. This is often seen if a database has auto-grown by a percentage value. If a customer wants to see a precise Size value for their database, it is better for them to use a query or possibly the built-in Disk Usage report. Please eliminate the displaying of any decimal values, or at least a maximum of one decimal-place, in the Size (MB)…

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

    We’ll send you updates on this idea

    1 comment  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  8. Unable to script out ExternalDataSource of type BLOB_STORAGE.

    It appears SSMS v17.7 does not know how to script out the external data source. I am getting this error when attempting to script out an existing data source.

    TITLE: Microsoft SQL Server Management Studio

    Unexpected value for enumeration type 5. (Microsoft.SqlServer.Smo)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=14.0.17254.0+((SSMSRel17_4).180502-0908)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.WrongPropertyValueExceptionText&LinkId=20476

    Attempting to look at Properties in the right click context menu also produces an error

    TITLE: Microsoft SQL Server Management Studio

    Cannot show requested dialog.


    ADDITIONAL INFORMATION:

    Invalid DataSourceType (SqlManagerUI)

    Here is the version information:
    Microsoft SQL Server Management Studio 14.0.17254.0
    Microsoft Analysis Services Client Tools 14.0.1016.251
    Microsoft Data Access Components (MDAC)…

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

    We’ll send you updates on this idea

    started  ·  6 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  9. SQL server Import and Export Wizard missing/disabled SSMS 18.0

    SQL Server import and export is disabled in SSMS 18.0, is this temporary and available in later versions of 18 or we wouldn't have import export going forward?

    5 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 →
    started  ·  Matteo Taveggia responded

    This is indeed an unintended removal. It only affected SQLEXPRESS.
    Thanks for the reporting it.
    We’ll fix it in a future release of SSMS 18.×.

  10. Appending datetime to the end of ""Commands completed successfully ... 2018-03-05 09:28:10.1829207"

    When I make any change to a stored procedure & compile it (F5),
    besides just returning ...
    "Commands completed successfully."

    Could we append a datetime to the end of that please ?
    "Commands completed successfully ... 2018-03-05 09:28:10.1829207"

    Buddy

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

    We’ll send you updates on this idea

    3 comments  ·  Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  11. SSMS 8.7 - CREATE OR ALTER is not supported for type ExtendedProperty. (Microsoft.SqlServer.Smo)

    in object explorer, triggers, right click, use 'create or alter to', new query editor window, and get this error

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

    CREATE OR ALTER is not supported for type ExtendedProperty. (Microsoft.SqlServer.Smo)


    Program Location:

    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ScriptCreateOrAlter(StringCollection query, ScriptingPreferences sp)
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ScriptCreateOrAlterInternal(StringCollection query, ScriptingPreferences sp, Boolean skipPropagateScript)
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ScriptCreateOrAlterInternal(StringCollection query, ScriptingPreferences sp)
    at Microsoft.SqlServer.Management.Smo.ScriptMaker.ScriptAlterObjects(List1 urns, Boolean isCreateOrAlter)
    at Microsoft.SqlServer.Management.Smo.ScriptMaker.ScriptUrns(List
    1 orderedUrns)
    at Microsoft.SqlServer.Management.Smo.ScriptMaker.DiscoverOrderScript(IEnumerable1 urns)
    at Microsoft.SqlServer.Management.Smo.ScriptMaker.ScriptWorker(List
    1 urns, ISmoScriptWriter writer)
    at Microsoft.SqlServer.Management.Smo.ScriptMaker.Script(Urn[] urns, ISmoScriptWriter writer)
    at Microsoft.SqlServer.Management.Smo.ScriptMaker.Script(Urn[] urns)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ScriptGenerator.ScriptCreateAlter(SqlTextWriter sqlwriter, Server server, Urn[] urns, ScriptingOptions options)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ScriptNodeActionContext.Script(SqlTextWriter writer)
    at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.SqlScriptMenu.OnScriptItemClick(Object sender, EventArgs e)

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

    We’ll send you updates on this idea

    started  ·  5 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  12. Replication Monitor Crashing with SSMS 17.8.1

    I installed SQL Server Management Studio 17.8.1 last night. This is from the About box:

    Microsoft SQL Server Management Studio 14.0.17277.0
    Microsoft Analysis Services Client Tools 14.0.1016.262
    Microsoft Data Access Components (MDAC) 10.0.16299.15
    Microsoft MSXML 3.0 4.0 6.0
    Microsoft Internet Explorer 9.11.16299.0
    Microsoft .NET Framework 4.0.30319.42000
    Operating System 6.3.16299

    This build has broken Replication Monitor. When I go to review the details of (for example) Distribution Agent Job Properties, it will crash with "Could not load file or assembly 'Microsoft.AnalysisServices.AppLocal, Version=14.0.0.0"..... The located assembly's manifest definition does not match the assembly reference."

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

    It turned out that UserVoice clipped the XML snipped I published (although it is there; you just can’t see).

    I’ve updated the steps with instructions on how to download a new version of the .config file, so you don’t have to edit it.

    I apologize for the inconvenience.

  13. SMO Server class spams AGs with failed blank user logins when used with SqlCredential

    When using SMO with a SqlCredential it may hammer the target server with failed connections to a blank username. These can be found in the SQL ERRORLOG. Interestingly SMO still appears to work but this prevents SqlCredentials from being used in production because it would trigger hundreds of thousands of failed logins every day.

    The problem is caused because somewhere in SMO it is not detecting the SqlCredential correctly.

    This does not happen on standalone servers. It does happen on servers in an AG, even when the SQL principal has sysadmin, and even with the server is a primary.

    I've…

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

    We’ll send you updates on this idea

    started  ·  2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  14. Unable to import module on powershell core 6.2.2 on linux

    When trying to import the SqlServer module on Linux I receive an error (see attached screenshot)

    I think I found the issue in this line $assessmentFormatFile = Join-Path -Path $PSModuleRoot -ChildPath "Microsoft.SqlServer.Assessment.Format.ps1xml"
    in the SqlServer.psm1 file.
    The actual file name is Microsoft.SqlServer.Assessment.format.ps1xml
    the F in the format is lowercase

    when changing the filename to match the code the import completes successfully.

    3 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. SSMS 18.5 forgets remembered passwords again

    This seemed to be working ok in 18.4 i hadn't had this issue since upgrading, but now in 18.5 it instantly started occurring again. Immediately after installing 18.5 in fact, the existing stored credentials showed the password had been forgotten again, even if i re-enter it and tick 'Remember', it'll be forgotten again if, for instance, my connection is dropped and i need to reconnect to the server.

    2 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. SSMS Import Flat File fails to import all data

    In SQL Server Management Studio 18.0 and 18.1, the following sample file defaults to INT NULL for the data type of the ID field and imports NULL for ID = 'abc'. This happens even if the data type of the field is set to NVARCHAR(50) NULL in the Modify Columns step. In this case the data type for ID in the created table is as requested, not INT NULL. If the data type is set to NVARCHAR(50) NOT NULL, it will generate an error (column 'Id' does not allow DBNULL). The expected behavior is to import all ID values as…

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

    We’ll send you updates on this idea

    started  ·  0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. SQL Server Management Studio v18.0 incorrectly displays database names

    I have experienced the described problem twice now. When working with databases in SSMS v18.0 the GUI displays incorrect names, and then continues processing with the incorrect database.

    For example, if the server has these databases:
    - DatabaseA
    - DatabaseB
    - DatabaseC
    - DatabaseB_Snapshot (being a snapshot of DatabaseB)

    Example a) 20190514: I needed to switch in one database for another by renaming through SSMS right-clicking...
    i) rename DatabaseA to DatabaseA_storing
    ii) rename DatabaseC to DatabaseA
    iii) rename DatabaseA back to DatabaseC
    result: now have two (2) DatabaseA's

    Example b) 20190510: I needed to clean up obsolete databases by dropping…

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

    We’ll send you updates on this idea

    started  ·  3 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  18. SSMS 18.0 - New Job Schedule Window Month Control Covered at High DPI

    At 175% DPI the month control is covered by a gray box and the value inside can't be seen.

    See attached screenshot.

    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 →
  19. SqlClient incorrectly decrypted and encrypted Always Encrypted data for UTF-8 collations

    The attached script demonstrates some bugs with the new UTF-8 collations and Always Encrypted. The script assumes that AE with enclaves is used, but that is only for convenience. My interpretation is that the issue is entirely in the client level.

    The script first creates an un-encrypted table with three text columns: one binary nvarchar column, one nvarchar column with a plain CS_AS collation and one varchar column using a UTF-8 collation. The script then adds three rows with the same text to all columns. The first is a Swedish word, the next is the English translation of that word…

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

    We’ll send you updates on this idea

    started  ·  2 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  20. SSMS Always Encrypted wizard makes incorrect collation change for UTF8 columns

    When you run the Always Encrypted wizard in SSMS 18 preview 6, and you select a column that has the collation FinnishSwedish100CSASSCUTF8 and then select a deterministic encryption, there is a warning triangle in the State column. That's normal, but the pop-up text says "The collation will be changed from FinnishSwedish100CSASSCUTF8 to FinnishSwedish100CsAcScUtf8" instead of the expected FinnishSwedish100_BIN2. If you don't observe this and continue, the wizard later fails, exactly with the message the collation is incorrect.

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

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

SQL Server

Categories

Feedback and Knowledge Base