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.
-
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.32 votesFixed in SSMS 18
-
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!
32 votes -
SSMS bug: missing ellipsis for truncated field values (Results to Grid)
This bug led me to think the values were different than actual ones: sometimes, when truncating values due to column width, SSMS 2017 (17.7) doesn't put ellipsis (…) in the end of the truncated value, and users are misled to think the value is not truncated.
29 votesPeter is correct. This appears to have been introduced with the Creators Update of Window 10. We reported this to them and in our testing this issue seems to be fixed with the October Update of Windows 10.
-
SSMS2018 - Installed, but will not run
Original post is here, with additional customer failure report: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/76236e43-dc82-4586-bf7f-b01ff6374462/ssms2018-installed-but-will-not-run?forum=sqltools
Windows 2016 Standard Edition. Brand new Hyper-V image. No prior SSMS on the server. Freshly installed SQL 2014, 16, and 17, Standard and Enterprise as 6 named instances. Restarted multiple times. Repaired the SSMS install. Restarted. I chose to install in a named folder: C:\Program Files (x86)\SSMS18 ..\Common7\ Size on disk: (1,090,367,488 bytes)
All that shows is the splash screen, then nothing. Run as administrator - I am a Local Admin - nothing.
Event Viewer - Nothing.
Uninstalled. Reboot. Reinstalled to default location.
WORKS FOR ME, but NOBODY ELSE on…
22 votesThe fix for this issue was included in SSMS 18.1.
Thanks,
-Matteo -
The DELETE key does not work as expected when trying to rename a database object in Object Explorer.
The DELETE key does not work as expected when trying to rename a database object in Object Explorer. The BACKSPACE key works correctly.
16 votesPlease, give SSMS 18.0 a try. The issue should be fixed now.
Thanks,
-Matteo -
SSMS 17.5 Intellisense not working for Azure Server
I am running SSMS 17.5 and attaching to an Azure server with 35 Databases and over 50 users.
If I connect to a local DB intellisense works fine. On the Azure server there is nothing. No Intellisense at all. It is turned on (TextEditor -> IntelliSense -> Enable Intellisense) and working against other servers.
My questions are:
Could this be a bug in SSMS 17.5?
Is there a setting in SQL server to disable Intellisense queries?13 votesThis has been addressed.
Please, give it a try on the latest version of SSMS (17.9 currently).
-
SSMS 17.6 crashes when clicking on a schedule in a maintenance plan
SQL Server Management Studio 17.6 (version 14.0.17230.0) crashes when I click on the schedule icon for a subplan (from a SQL Server 2016 SP1 CU4 instance). In Event Viewer, I find the following event from ".Net Runtime":
Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.SqlServer.Management.SqlMgmt.ScheduleDialog.InitializeControls()
at Microsoft.SqlServer.Management.SqlMgmt.ScheduleDialog..ctor(Microsoft.SqlServer.Management.SqlMgmt.JobScheduleData)
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.ChangeShedule()
at Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.grid_MouseButtonClicked(System.Object, Microsoft.SqlServer.Management.UI.Grid.MouseButtonClickedEventArgs)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseButtonClicked(Int64, Int32, System.Drawing.Rectangle, System.Windows.Forms.MouseButtons)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.HandleButtonLBtnUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.ProcessLeftButtonUp(Int32, Int32)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnMouseUp(System.Windows.Forms.MouseEventArgs)
at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)12 votesThis is fixed in the current version of SSMS, as it was mentioned below.
-
SSMS 17.6 Crash when opening scheduler task for a maintenance task
When conencting for far to
2012 sp3
2014 sp2
2016 sp1I crash anytime I try to open the scheduler task, I still had a VM with 17.4 and this works correctly on the same versions.
New or already created one. No time to enter or modify as it crash on load.
Event id 1000
Faulting application name: Ssms.exe, version: 2017.140.17230.0, time stamp: 0x5aa77b02
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x15723a35
Faulting process id: 0x163c
Faulting application start time: 0x01d3c19109d5c915
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe
Faulting module path: unknown …11 votesThis should be fixed in the current version of SSMS.
It’s a duplicate of https://feedback.azure.com/forums/908035/suggestions/33712924.
If you think it is not fixed (or you see something else wrong), please open a new UserVoice item and provide more detailed steps so we can investigate further. Thanks!
-
Unable to horizontal scroll Results pane via mouse wheel in SSMS
My mouse has a horizontal scroll wheel. I can use the horizontal scroll in the Query pane, but if I select the Results pane, I can't scroll horizontally using my mouse. If I scroll to the left by dragging the scroll bar, and then try to use the horizontal scroll wheel on my mouse, the Results pane snaps to the leftmost position.
10 votesPlease, install SSMS 18.2 which has the fix.
Thanks,
-Matteo -
Batch mode window aggregate arithmetic overflow bug
The following query performs a windowed SUM over a columnstore table with 1500 total rows, each of which has the value 0 or 1, and it overflows the INT data type. This appears to be a bug in the batch mode window aggregate operator.
SELECT a, p, s, v, m, n,
SUM(CASE WHEN n IS NULL THEN 0 ELSE 1 END)
OVER (PARTITION BY s, v, a ORDER BY p) AS lastNonNullPartition
FROM (
SELECT a, p, s, v, m, n,
RANK() OVER (PARTITION BY v, s, a, p ORDER BY m) AS rank
FROM #t /* A columnstore table…9 votescompleted ·
AdminSQL Database feature voting forum admins
(Product Owner, Microsoft Azure)
responded
Thank you for reporting. This is fixed in SQL Server 2019 CTP 2.1 and will also be fixed soon in Azure SQL Database.
-
SSMS 17.3 Font and Color setting limit changes to 4 areas
After upgrading to ver. 17.3 of SSMS 2017, I am unable to enlarge the default font size used for grids or the object explorer (Environment Font). After running a search I several posts in the SQL Server Forum, but after trying the fix mosts sided, which was uninstalling 17.3, then install 17.2 and do the upgrade to 17.3. This was ineffective for me and others.
Under "Show settings for:" instead of listing all the options that should be listed, I see only the following. This is obviously a bug. Has anyone found a solution that fixes this problem?
9 votesPlease, install SSMS 18.x (currently SSMS 18.2) which should not present this issue anymore.
Thanks,
-Matteo -
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.
8 votes -
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)"8 votesThis issue has been fixed in the new major version of SSMS 18.0 (currently in Preview). Please, have a look.
Thanks,
-Matteo -
SSMS Install with SQL Server 2016 causes Device Manager conflict on VS location sensor driver
If you take (as an example) a clean machine, with no VS or SQL Server yet, install SQL Server 2016 (say community but doesn't matter), Device Manager is fine, no conflicts (no VS location sensor driver yet)...Then you install SSMS (production/GA version 16.5.3), you get a Device Manager conflict (yellow exclamation mark/can't load driver error) on a new sensor entry called "Microsoft Visual Studio Location Simulator Sensor".
8 votesPlease, use the latest SSMS (18.2 as of yesterday) which does not have this problem anymore.
Thanks,
-Matteo -
Incorrect GrantedQueryMemory(KB) Value on SQL Performance Dashboard or SSMS17.9
The inbuilt SQL Dashboard within newer versions of SSMS displays report for GrantedQueryMemory(KB) column for current request sub report. The value displays the wrong number as output displayed is in bytes while column says KB.
I have verified using the dmv "sys.dm_exec_query_stats" which lists this number in no.of pages which later is converted to KB
When checking within rdl file we can see that conversion is made with expression as =8192 * Fields!granted_query_memory.value which gets this value in bytes.
Therefore we might need to change that expression to = 8 * Fields!granted_query_memory.value
7 votesPlease, install the latest version of SSMS (18.2+) which has the fix for this issue.
Thanks,
-Matteo -
SSMS pop-up windows/forms on same screen where SSMS window is active.
When right clicking in the object explorer on an element, i.e., "Tables" and wanting to perform an action such as filtering tables by going to Filter > Filter Settings, the filter settings form can appear on the other screen than where SSMS is currently active -- which is quite distracting.
I believe this is due to the initial position of SSMS on startup. If you move the SSMS window to another screen, the opening of forms/windows etc. will remain on the original screen and not follow the main SSMS window.
Watch this clip: https://d.pr/v/v7dq8v
Notice that you can only see…7 votesWe fixed the issue with the OE filter dialog in SSMS 18.0 Preview 4. Please, let us know if that works for you and let us know about other places you may have observed this incorrect behavior. Thanks!
-
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 votesWe believe this should be fixed in the latest version of SSMS.
please open a new ticket if the issue still persists..
thanks,
Dinakar -
SSMS - Grid Results Background Colour
Please can you fix the issue with the grid results background colour being ignored in SSMS? If you try and change the colour, it always stays at white. This bug has been around since SQL 2005!!! Surely it's just one line of code, "background.color=xxxx"? - How can you let this bug drag on for at least 11 years!! The dark themes in Visual Studio work perfectly, why can't we have this is SSMS?
6 votesWe have fixed this issue in SSMS 18.0 RC1 which you can download here https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017#ssms-180-rc1
Thanks again for reporting this issue.Erica
-
After SSMS Update to v17.8.1 I get Could not load file or assembly 'Microsoft.AnalysisServices.AppLocal
Don't really use replication server, so I didn't think this fit into that category, but the update to SSMS certainly messed up something....
After updating my SSMS from v17.7 to v17.8.1, I get the following error. I also have Visual Studio Professional v15.7.5 and SQL Server 2017 Developer Edition. Yesterday, uninstalled SSMS, repaired VS v15.7.5, and reinstalled SQL Server 2017 Developer, which took forever, but everything seemed to run fine. I was up and running and then I usually restart my machine when I leave and when I logged in this morning, I'm getting this error again (I'm assuming the…
5 votesThis should have been fixed by now.
Also, while at it, consider giving the new SSMS 18.0 (which is currently in Preview) a try!
Thanks,
-Matteo -
SQL Management Studio Copy Database Wizard Broken
Copy Database Wizard is not working for local copy operation. v17.5 There are previous bug reports when trying to copy a SQL201x -> SQL2017 DB using management studio 17.x . However, it appears you cannot copy a SQL2017-SQL2017 DB as well using the same wizard using the SMO option when copying without taking the DB offline. ERR: Property HasMemoryOptimizedObjects is not available for Database '[test]'
File attached5 votesThis was fixed in SSMS 17.9. Thanks.
- Don't see your idea?