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.
-
SSMS: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…
453 votesWe’ll look at this for future release.
-
Add AAD Auth to Invoke-SqlCmd
Please add Azure Active Directory authentication as an option for the Invoke-SqlCmd cmdlet to connect to an Azure SQL DB.
34 votesCool. It was already on my backlog…
Thanks,
-Matteo -
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.27 votes -
Performance Dashboard / Expensive Queries / copy query text
When using the reports in the SSMS Performance Dashboard, you are unable to copy the query text from any of the "expensive queries" reports. Make it so you can either click to view the query in a new query window, or right-click the query to copy the text for pasting into a new window.
20 votes -
Database diagram kills SSMS
When i want to open an existing diagram in SSMS 18.2 on a database which is on compativity level 100 SSMS closes and restarts immediately. I also tried it with a new diagram - this seems to work.
12 votesThanks for reporting this issue.
Sadly, I am well aware of issues with Diagrams since I brought them back in SSMS 18… You should find another UserVoice item here with plenty of understandable upvotes (https://feedback.azure.com/forums/908035/suggestions/37992649).
Unfortunately, it is proving to be pretty complex to deal with this this ancient technology that is used by SSMS.
-
Remove Brackets from SSMS script generation
I won�t argue technical merits and I doubt this will sway the 800 lb. gorilla. But all one need do is listen to the chatter on the internet to realize that the use of brackets in SSMS script generation is a royal PIA. I respectfully request an option to remove them in SSMS. At the end of the day, you know this can be done and it would make a whole lot of of MSFT customers happy. Thank you.
11 votesI don’t have a date for this but we’ll start making progress on this. When we fix this in SqlManagementObjects then it will show up in SSMS, mssql-scripter, and SQL ops studio.
-
SSMS 17.3 excessive memory usage
SSMS consumes large amounts of memory & CPU, even when idle. Disabling intellisense has no effect
11 votesThanks for bringing it up to our attention (once again).
-
Registered Server modifications via SQLServer PowerShell module bug
There is an apparent bug in version 21.1.18068 of the SQLServer PowerShell module when creating Registered Servers groups and registrations. When created at the PowerShell prompt they are not reflected in the Registered Servers window (even after refresh, or reboot). Existing groups and registrations seen in the Registered Servers window are not available at the Powershell prompt using commands such as dir or Get-ChildItem.
The commands I use to create groups and registrations at the PoweShell prompt are similar to:
group
New-Item -Path "sqlserver:\SQLRegistration\Database Engine Server Group\AllServers"
registration
New-Item -Name $(encode-sqlname 'sqlsrv') -path "sqlserver:\SQLRegistration\Database Engine Server Group\AllServers" -ItemType Registration -Value…
6 votesThanks for the suggestion. We are going to take a look and get back to you.
-
Set the Maximum Size of the SQL Server Error Logs
In SQL Server 2012 and later versions, you can use xpinstanceregwrite to set the maximum size of individual error logs. Please make this setting available via SMO, instead of having to use xpinstanceregwrite.
Documentation for this feature can be found here: https://support.microsoft.com/en-us/help/2199578/how-to-manage-the-sql-server-error-log
6 votesI’ll get this going for 17.7
-
SSMS: Allow forcing case-insensitive matching in Object Explorer filters
In SSMS, when filtering objects in Object Explorer, comparisons on string properties (e.g. Name) use the collation of the database or instance, depending on whether you are filtering database-level or instance-level meta-data, respectively. Hence, when either level is using either a case-sensitive or binary collation, it is not possible to do a case-insensitive search of objects at that level. Having a "case-insensitive" check-box per each filterable Property would be super awesome 😺. Even better might be a "flip case sensitivity" check-box that would then also make it a case-sensitive comparison in an otherwise case-insensitive context.
This situation lead to the…
5 votesThanks for filing this request. We’ll take a look at it and prioritize.
-
SSMS: Object Explorer Filtering allows for SQL Injection (oops)
When applying filters in Object Explorer (in any "Filter Settings" dialog) in SSMS 17.9.1 and 2018 Preview 6 (and possibly versions prior to 17), it is possible to inject SQL into the query executed by SSMS, simply by using a single quote / apostrophe. Yes, the app code clearly escapes a single apostrophe into two apostrophes, but the string containing the apostrophe is concatenated into a Dynamic SQL string executed via sp_executesql. The string entered via the UI to filter on is intended to be used within a string literal within the Dynamic SQL string. In this case I filtered…
5 votesThanks for reporting this issue. We’ll take a look at it.
-
SQL Server 2019 Master Data Service: Number editing fails
Upgraded SQL 2017 MDS to SQL 2019 RTM. Editing an decimal value of an entity fails when regional language is set to german. Can't use "," as an decimal seperator, When language set to an english then editing works fine when using "." as decimal seperator
4 votes -
SSMS Removes comments when Enable Parameterization for Always Encrypted checked
When you have Both of these settings
In the Connection Properties of the Connect to Database Engine, go to Additional Connection Parameters and enter the following: Column Encryption Setting=Enabled
Right click on your query pane and to go Query Options => Advanced => select Enable Parameterization for Always Encrypted
Now try to alter a proc that has comments in it
Viola. Comments are gone and all lines have been reformatted to put a SQL Command into a single line.
4 votesThis is indeed an issue. Thanks for reporting it.
Note: it is also the same as https://feedback.azure.com/forums/908035/suggestions/32895916
-
SSMS 18 opens wrong server log
SSMS 18.0 always opens the current server log even if you've double-clicked an older archive log in the object explorer.
3 votesThanks for the reporting the issue. We’ll take a look at it and prioritize accordingly.
-
PowerShell get-item for SSIS package returns "number of keys" error
PS SQLSERVER:\SSIS\VDEMO\DEMO\Catalogs\SSISDB\Folders\Demo\Projects\Deployment\Packages> $pkg = get-item 'Package.dtsx'
Get-Item : Cannot retrieve the dynamic parameters for the cmdlet. SQL Server PowerShell provider error: The number of keys specified does not match the number of keys required to address this object. The number of keys required
are: Name.
At line:1 char:8
+ $pkg = get-item 'Package.dtsx'
+ ~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : InvalidArgument: (:) [Get-Item], ParameterBindingException
+ FullyQualifiedErrorId : GetDynamicParametersException,Microsoft.PowerShell.Commands.GetItemCommand3 votes -
SSMS 17.3 IntelliSense does not recognize CATALOG_DEFAULT as a valid collation
Management Studio, with IntelliSense enabled, does not seem to know that "CATALOG_DEFAULT" is a valid collation option. The name is underlined in red with a tool tip of:
Invalid Collation 'CATALOG_DEFAULT'.
Yet, it clearly is not invalid since it does work :-).
I have observed this behavior in SSMS 17.1 and now in 17.3.
I have tested with both SQL Server 2012 and 2016.
3 votesThanks for the reporting the issue. We’ll take a look at it and prioritize accordingly.
-
Data Collector 2017 exception 0xc0000409
We receive this error when attempting to run the data collector for Sql Server 2017 CU11
Faulting application name: dcexec.exe, version: 2017.140.3038.14, time stamp: 0x5b9c1fca
Faulting module name: DTS.dll, version: 2017.140.3038.14, time stamp: 0x5b9c1f91
Exception code: 0xc0000409
Fault offset: 0x00000000001437f4
Faulting process id: 0xd38
Faulting application start time: 0x01d454f46156026f
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\Binn\dcexec.exe
Faulting module path: c:\Program Files\Microsoft SQL Server\140\DTS\Binn\DTS.dll
Report Id: 09692622-b45f-4a7c-8951-6ac410174dbf
Faulting package full name:
Faulting package-relative application ID:Strangely, the Query Statistics collection runs without issue, but the Disk Activity and the Server Activity collection sets will not run.
2 votes -
Add SubSystem Property to Get-SqlAgentJobStep Default Output
Please add the SubSystem property to the default output of the Get-SqlAgentJobStep cmdlet. Adding this to property to the default output will make it more obvious to customers that they can easily filter their results when searching for things like 'Jobs which contain a Step-Type of SSIS package'.
(Please also consider making the Name property 10-charachters wider by default.)
2 votesThanks for the suggestion.
-
Scripting Delete action to new query window is deleting the maintenance plans without even executing the script
SQL Server version: Microsoft SQL Server 2014 (SP2) (KB3171021) - 12.0.5000.0
Tested using SSMS 17 and SSMS 12Scripting Delete action to new query window for Maintenance plans is deleting the maintenance plans without actually executing the script:
Steps:
1)Create a maintenance plan using maintenance plan wizard
2)This creates maintenance plan under path : Server or Instance Name>Management>Maintenance Plans along with a corresponding job under Sql server agent when viewed from SSMS
3)Now right click on the Maintenance plan that gets created from step 1 in location specified in step 2 above and click delete
4)But instead of clicking OK…2 votesthanx, we’ll look into a fix for a future release to help avoid data loss.
-
breaking changes sql server 2019 preview
Hi, I know that SQL Server 2019 is still in CTP and hasn't released yet, but I haven't seen the "Breaking Changes to SQL Server 2019" document yet like the one for 2017 at https://docs.microsoft.com/en-us/sql/database-engine/breaking-changes-to-database-engine-features-in-sql-server-2017?view=sql-server-ver15 .
Does anyone know when this will be released and if there are any breaking changes for SQL Server 2019? I'm just curious since we are planning on a SQL Server 2019 upgrade project in the near future once it's released.
Thank you!
Mike Petrak1 voteHello Mike
As we get closer to General Availability, rest assured that will be covered in the documentation.
thanks,
Dinakar
- Don't see your idea?