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.
-
Unable to deploy SSIS packages from Visual Studio 2017 (15.8.0)
The latest version of Visual Studio 2017 (15.8.0) appears to have introduced a bug preventing deployment of SSIS project files.
When attempting to connect to a server the deployment wizard returns the following error:
TITLE: SQL Server Integration Services
------------------------------Could not load file or assembly 'Microsoft.SqlServer.Management.IntegrationServicesEnum, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)
------------------------------
ADDITIONAL INFORMATION:The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)
------------------------------
BUTTONS:OK
------------------------------361 votes -
Optimise for Analytics configuration option
Would love to have a new Server-Wide as well as the Database Scoped Configuration configuration that would be called "Optimise for Analytics" and that would server the purpose of tuning the Storage Engine & Query Processor specifically for the Analytical Workloads (Business Intelligence, Data Warehousing, Data Preparation for ML, etc).
The actual functionalities to be controlled by this option would be such as: -E configuration, Query Optimiser huge preference for the Hash Joins, Bigger preference for the Batch Execution Mode for the Rowstore tables, Bigger preferences for the Scans and Prefetching for the Storage Engine, Bigger Columnstore Object Pool allocation…
95 votes -
Run DBCC CHECKDB WITH PHYSICAL_ONLY automatically in the background
When RAID controllers are idle, they automatically check the storage to make sure it's still okay. Why not SQL Server too?
Some of the pieces are there – for example, SQL Server already has the ability to watch for idle CPU times and run Agent jobs when it’s bored. For starters, that’d probably be good enough to save a lot of small businesses from heartache. For the databases over, say, 100GB, it’d be really awesome to have resumable physical_only corruption checking – tracking which pages have been checked (just like how the differential bitmap tracks page changes), with page activity…
331 votesThis aligns with our vision for improved manageability, particularly for VLDBs. Will consider for future development.
-
Option to specify a location for the DBCC CHECKDB snapshot
When you run DBCC CHECKDB, by default the snapshot is stored on the same drive as the database data file(s).
It would be nice to be able to specify the location, if you have
- Faster drives elsewhere
- No space on the same hard drive
- Less I/O traffic elsewhere87 votes -
Database Level Option For Storing Wait Stats
SQL Server 2016 introduced Query Store, and SQL Server 2017 CU3 brought us aggregated wait stats at the query level. This is great information for data driven DBAs who need to be able to track plan changes over time, etc.
With that in mind, an additional data collector for wait stats per database would be a great product feature, independent from Query Store data collection.
We all know the limitations of the wait stats DMVs now:
- They're cumulative over time
- They're instance-wide
- There's a lot of potential noise from wait types that aren't registeredIf you wanna…
226 votes -
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…
91 votesCMS (RegisteredServers) has been ported. It will be included in the next version of SMO and/or the next version of the SQL Powershell module.
-Matteo
-
Support DISTINCT for STRING_AGG
Currently STRING_AGG aggregates all strings passed as an input. It would be very useful to support DISTINCT, so it would concatenate unique strings only.
Example:
CREATE TABLE dbo.Test (a VARCHAR(255))
INSERT INTO dbo.Test (a)
VALUES('Str1')
,('Str2')
,('Str1')SELECT STRING_AGG(a, ',') FROM dbo.Test t
It returns: 'Str1,Str2,Str1'
SELECT STRING_AGG(DISTINCT a, ',') FROM dbo.Test t
It would return: 'Str1,Str2'
72 votes -
SSDT for Visual Studio 2017 - Include as part of the VS 2017 Installer
Can we please pass over the SSDT components to the Visual Studio team so this can be included as part of the Visual Studio 2017 installation process?
The VS team can then build out the installer in a way that SSDT is always compatible with their latest build and installer. We've been stuck with the break fix break fix loop with SSDT and incompatibility with VS upgrades for too long now. The SSDT team doesn't respond quickly enough, the latest example being SSDT 15.6/VS 2017 15.7.x installation issue, why are we waiting so long for an installer update?
144 votes -
Dark Theme for SQL Server Management Studio 2017 (SSMS 2017)
Dark Theme works well in Visual Studio and should be included in SSMS. It helps reduce eye strain after long periods of development and debugging.
361 votes -
Explain why indexes were skipped
Feature request: expose information about what indexes the optimizer considered while compiling an execution plan. Specifically, the index names and WHY the index was rejected for that particular query. This could potentially be included in per-operator execution plan properties (see attached mockup), an extended event target, or some other avenue.
Reason: many developers and DBAs wonder why certain indexes on their tables aren't being chosen for specific queries. This gives them better tools to figure that out and make better use of the SQL Server product.
I've blogged about this feature request in more detail here: http://joshthecoder.com/2018/06/21/feature-request-index-rejection-reasons.html
This request was…
119 votes -
Add SSIS to the SQL Server Docker Image
I work for a large bank which it trying to move hundreds of SSIS packages into GitLab pipelines. This task would happen faster an easier with SSIS on the MS SQL Server Docker image.
65 votes -
SQL Server Assertion: File: <lobss.cpp>, line = 725 Failed Assertion = '0' Should never happen.
DBCC CHECKDB reports no errors, I rebuilt the indexes just to be sure. It happens when running this query:
WITH t1 AS
(
SELECT [Endpoints].[Name] AS [f1],[MatchLocations].[Location] AS [f2],ISNULL(SUM([Matches].[LastCount]), 0) AS [f3],ROW_NUMBER() OVER (ORDER BY [Endpoints].[Name] ASC) AS [f4]
FROM MatchLocations
INNER JOIN [Matches] ON ([MatchLocations].[Id] = [Matches].[MatchLocationId])
INNER JOIN [Endpoints] ON ([Endpoints].[Id] = [MatchLocations].[EndpointId])
GROUP BY [Endpoints].[Name],[MatchLocations].[Location]
)
SELECT [t1].[f1] AS [t1_f1],[t1].[f2] AS [t1_f2],[t1].[f3] AS [t1_f3]
FROM t1
WHERE ([t1].[f4] BETWEEN 1 AND 100)
ORDER BY [t1].[f4] ASCWhen the SUM and GROUP BY are removed, it runs just fine. It happens from time to time on some databases,…
19 votes -
Add a Keyboard Shortcut that Executes the Statement where the Cursor is placed
Having to select statements by clicking and holding the mouse is just bad ergonomics. Request to have a keyboard shortcut which runs the current sql statement. The current sql statement is defined based on where the cursor is placed. For example, proposed shortcut runs only runs a single sql statement to the next semicolon. This shortcut would be an equivalent to Oracle's SQL developer's ctrl + enter shortcut. Note that this is probably the most used shortcut in SQL Developer and not having an equivalent on SQL Server Management Studio is disappointing. I know that not everyone ends their statements…
290 votesWe’ll look at this for future release.
-
Microsoft Command Line Utilities 15 for SQL Server fails to recognize pre-requisite ODBC 17
SQLCMD docs state that Command Line Utilities 15 requires ODBC 17 (https://docs.microsoft.com/en-us/sql/tools/sqlcmd-utility?view=sql-server-2017). However, the actual Command Line Utilities 15 installer does not recognize a previously installed ODBC 17.
Installing ODBC 13 will allow the Command Line Utilities 15 installer to complete successfully, but we end up with errors later presumably due to the Command Line Utilities 15 actually requiring OBDC 17 functionality. Installing both versions 13 and 17 seems to get around this, but obviously requires installation of both packages.
Our server for testing this is a 64 bit Windows 2008 R2 Enterprise with SP1.
Repro steps:
-…22 votes -
adomd core
ADOMD.NET Client Needs .NET Core Support
Please tell us when this will be available. We've been waiting years, and all ADOMD.NET does is XML over HTTP - it's pretty silly that there's no support for clients running on .NET Core!
35 votes -
SSAS Designer showing empty phantom/duplicate tables
Working with an SSAS multidimensional cube that was developed using SSDT 17.3, the Data Source View for the cube is showing multiple phantom tables as the data source view is changed/refreshed. This is happening when looking at the Data Source View for both cubes as well as dimensions.
The Data Source View object itself does not show any issues, cube functionality does not appear to be affected when it is deployed and processed.
When trying to use the "Copy Diagram from" function, Visual Studio crashes on me.
The issue has persisted as I've upgraded to 17.4, as well as testing…
53 votes -
develop a SSRS ReportViewer for ASP.NET Core
Develop a SSRS ReportViewer for ASP.NET Core
185 votes -
Trigger symbol on tables and views in object explorer
In SSMS Object Explorer, you can find DML triggers by expanding the table (or view) and then expanding the Triggers node. That is fine.
However, it would be great to have a visual indication, as a kind of warning, on the table or view symbol. This symbol should only appear on tables and views that have one or more active triggers
My suggestion for the symbol would be a lightning bolt (similar to the icon used for the actual triggers). Preferably in red.31 votes -
Database diagrams on new release 18 not work
I installed SSMS 18.0 and cannot find Database diagrams folder. It is just missing. Where is the problem?
15 votes -
Put Debugger back into SSMS 18
The SSMS Debugger is critical for debugging complex T-SQL Queries, please return it to SSMS 18
20 votes
- Don't see your idea?