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.
-
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…
257 votesWe’ll look at this for future release.
-
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…
69 votes -
Visual Studio 2017 SSDT adds hardcoded master.dacpac include
Visual Studio 2017 seems to add a hardcoded path to the master.dacpac if I include it in a project of mine. Older versions of the SSDT used the $(DacPacRootPath) variable to get the master.dacpac.
This is really annoying as it breaks the builds on our build server where the master.dacpac is installed in a different folder than on my development machine.
52 votesCurrently investigating a fix, and we’ll try to get this in a future update.
-
Remove the word "Initial" in SSMS, Object Explorer, Database Properties, Files.
Right-click a database, Properties, Files. There's a column named "Initial Size (MB". The word "Initial" should be removed. It is incorrect to have that word there. What we see here is the current size. This is particularly confusing for tempdb since people tend to think that what you see here is indeed the initial size (size at startup, from sys.master_files), which is *not* correct. Again, you see the current size!
27 votesWe will investigate this for a future release.
-
SSMS 2016 does not remember added SQL Snippets folder
You can add your own snippets in SSMS bij using the Code Snippet Manager.
In the Code Snippet Manager window you have the possibility to add a folder containing customer snippets by using the "Add..." button.
This works fine as long as you're not closing SSMS. After restarting SSMS you have to add the folder again because it is no longer available in the snippets.22 votesThanks for the feedback. We’ll take a look.
-
SQL History SSMS
In SSMS, keep track of all SQL run within SSMS and enable recall to run again. Store in local file/db. Do not store results but do store result stats. Such as Execution Time, Number of rows returned, date executed.
Click to open in new window. Allow choice of connection to run against.
17 votes -
Move SSMS and Updates into WSUS
I want to control SSMS and updates via WSUS. Please add to the catalog for importing or add to Products under SQL Server in the WSUS catalog.
16 votesWe will investigate this for a future release.
-
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.16 votes -
Azure AD authentication in Import Export wizard in SSMS
Ssms 2017 doesn't have the capability to use Azure AD authentication in Import/Export wizard.
We have stopped providing Sql authenticated users to support people, we are using AD authentication which works seamlessly. However there is one more place in SSMS which requires the functionality.When users try to use import export wizard they dont have possibility to use Azure AD authentication instead they need to use a SQL authentication which completely ruins our security setup and going back to the old way of accessing Azure Sql db.
Can the SSMS team add this little functionality so that it does in…
15 votesWe’ll investigate for a future release.
-
SQL Server Management Studio - search interface bug, crashing SSMS
There is a bug in SQL Server Management Studio (17.9 and all below) that force the application to crash/restart. In order to reproduce follow the steps below:
1. Select database from the object explorer
2. Press F7 to open Object Explorer Details window and perform a search to object
3. After the search completes, select the object, right click on it and then click "synchronized" from the menu.
4. Then click the `BACK` button several times (fast). You will get the following error:"There is already a commandd handler for the menu command 'guid goes here: 189."
After several clicks…
13 votesThank you guys for reporting the issue. We will be taking a look as soon as possible.
-
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.
13 votes -
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)…
9 votes -
SSMS 17 Tools > Options > Environment > Fonts and Colors missing Display items
In a generic SSMS 17.2 install on a Windows 7 64-bit workstation, if I open Tools > Options > Environment > Fonts and Colors, I only get 3 items in the 'Display items:' list: Plain Text, Selected Text, and Inactive Selected Text. I have no options to change anything else. In my SSMS 2016 install, I have over 200 items in the 'Display items:' pick list. Comparison screenshot here: https://imgur.com/a/XiGMm
I have tried resetting all settings to default in the Import and Export Settings Wizard. No change.
8 votesHello
We are trying to setup a repro in-house.
Will post an update once we are able to do so..thanks,
Dinakar Nethi -
Locate backups in azure container fails when Shared Access Signature contains sip parameter
1. I have a SAS created as here: https://docs.microsoft.com/en-us/sql/relational-databases/lesson-1-create-stored-access-policy-and-shared-access-signature, but i added ip restrictions (IpRange argument in GetSharedAccessSignature ), so that sas contains paramter sip=x.x.x.x-y.y.y.y
2. When I use this SAS in SSMS 17.4 to restore the backup, then in the "Locate Backup File In Microsoft Auzre" popup i cannot see any files. The reason is that SSMS issues invalid rest call, as it does not include the sip parameter, and that is the reason why the call is not authorized.7 votes -
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.
6 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.
-
new TRANSLATE function syntax not recognized by SSMS 17.3
The new TRANSLATE function is not recognized as valid syntax by SSMS 17.3 intellisense, though it executes just fine against SQL Server 17 instances. The TRANSLATE syntax is underlined in red with the warning "'TRANSLATE' is not a recognized built-in function name"
Tested against SQL Server 17 RTM.
6 votesThanks for reporting the issue. We’ll look into fixing it in the next major release of SSMS.
-
SSMS v17 - Object must implement IConvertible. (mscorlib)
When a query is selected with the mouse/keyboard, and then "Analyze Query in Database Engine Tuning Advisor" option in the context menu is selected the following error appears.
"The argument type 'server type = Sql, server name = KSHQ-DB, timeout = 30, database = KSH_Cloudcare, protocol = NotSpecified, workstation = , integrated security = True' cannot be converted into parameter type 'Microsoft.SqlServer.Management.Common.SqlConnectionInfo'. (mscorlib)
Object must implement IConvertible. (mscorlib)"6 votesThis is a known issue and it is being fixed (probably in the next major release of SSMS).
Aside from the workaround listed here (update the dtashell.exe.config), another “workaround” is to upgrade from a previous version of SSMS 17.x (e.g. going from 17.4 to 17.5): that has the nice side effect of fixing the dtashell.exe.config as well.
-
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
4 votes -
Unable to Invoke-SqlVulnerabilityAssessmentScan via PowerShell to run SQL Vulnarability Assessment Tool.
We are looking to call the Invoke-SqlVulnerabilityAssessmentScan to run the SQL Vulnerability scans via PowerShell.. We want to invoke this call for all the SQL Databases in the SQL Instance and want to export the JSON files into a folder.
Here is the command via PowerShell:
Invoke-SqlVulnerabilityAssessmentScan -ServerInstance "<SQL Server Name>" -DatabaseName "<DatabaseName>" -ScanId "Scan_01"
We are getting the following error:
Invoke-SqlVulnerabilityAssessmentScan : Error setting value to 'c_schema' on 'DataSec.VA.Core.Model.RuleDefinition.VARuleSet'.
At line:10 char:4
+ Invoke-SqlVulnerabilityAssessmentScan -ServerInstance $instance_w ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Invoke-SqlVulnerabilityAssessmentScan], JsonSerializationException
+ FullyQualifiedErrorId : Newtonsoft.Json.JsonSerializationException,Microsoft.SqlServer.Management.PowerShell.VulnerabilityAssessment.InvokeVulnerabili
tyAssessmentScanCould you please help us address this issue.…
3 votesInvestigating
-
Set the Maximum Size of the SQL Server Error Logs
In SQL Server 2012 and later versions, you can use xp_instance_regwrite to set the maximum size of individual error logs. Please make this setting available via SMO, instead of having to use xp_instance_regwrite.
Documentation for this feature can be found here: https://support.microsoft.com/en-us/help/2199578/how-to-manage-the-sql-server-error-log
3 votesI’ll get this going for 17.7
- Don't see your idea?