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.
-
binary or string data would be truncated => error message enhancments
if you have that error (in production), it's not obvious to see which column or row this error comes from, and how to locate it exactly.
it's even more complicated if it's coming from a trigger, for example, and not the original insert/update.I have seen that oracle meanwhile gives clear information which column the error is raising, which actual data length was passed, and the column's max size.
1,156 votesThis feature is shipped in SQL Server 2017 CU12, SQL Server 2019 CTP and upcoming SQL Server 2016 CP2 CU. Read more at https://blogs.msdn.microsoft.com/sql_server_team/string-or-binary-data-would-be-truncated-replacing-the-infamous-error-8152/
-
Database Diagram
hello this version should have database diagrams, this tool is very util
114 votesClosing as completed (please upgrade to SSMS 18.1+)
Thanks,
-Matteo -
Give us option to not have square brackets when drag&drop in SSMS
When we drag something from OE into a query window, then the identifier will always be enclosed in square brackets. Many of us do our due diligence and take care to use identifiers that do not require separators. These separators makes SQL code (a lot) harder to read, and we feel that we are punished with these square brackets. We don't want to do a search and replace all over and over again, when there could just be a setting in SSMS to not generate these.
61 votesssms 17.6 has Tools/Options settings to turn off schema inclusion and bracket escaping of object names during drag/drop. Names that include spaces or closing brackets will always be escaped.
-
String or binary data would be truncated
Msg 8152, Level 16, State 13, Line 2
String or binary data would be truncated.
The statement has been terminated.A lovely error in a 300 lines of SQL update statement in SQL Server 2005, it does not say what field was truncated, what line was truncated.
41 votesThis feature is shipped in SQL Server 2017 CU12, SQL Server 2019 CTP and upcoming SQL Server 2016 CP2 CU. Read more at https://blogs.msdn.microsoft.com/sql_server_team/string-or-binary-data-would-be-truncated-replacing-the-infamous-error-8152/
-
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 -
Add Default Backup Checksum Option to SSMS GUI
SSMS should have a checkbox under Server Properties, on the Database Settings page, labeled something like "Use Backup Checksums" that would toggle the sp_configure setting for "backup checksum default". This would make it easier for people to enable backup checksum default, which is a good "best practice" that the tooling should encourage.
21 votesCheck out SSMS 18.0 Preview 4 where we have added this option to the UI.
This is a Preview Release so please take that into account before installing.
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017&branch=release-sqlseattle- Erica Pettit
-
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 Still Forgets Passwords
You closed this same issue many times as, variously, norepro and wontfix. However, this is a serious, long-standing issue for those of us unfortunate enough to have to manage numerous SQL Server deployments.
This is a known, reproducible issue, as you can tell from the many Google results, as well as the comments on the many reports of this bug you've ignored. Below is the description of the bug from my last report, which was closed as wontfix with no explanation.
SQL Server Management Studio (SSMS) has a long-standing bug that you refuse to fix. Below are some of the…
15 votesFor SSMS 18 we moved the passwords into Windows Credential manager so they can be encrypted and decrypted more reliably.
-
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!
-
Make Scalar UDF with no data access running parallelly
There are different scalar-value UDFs:
- (1) Interpreted T-SQL UDF,
- (2) Natively Complied T-SQL UDF and
- (3a) CLR UDF with DataAccessKind.None, which is default option.
- (3b) CLR UDF with DataAccessKind.Read.For CLR UDF, if its USERDATAACCESS = 0, then it�s not a parallel plan blocker.
For other type of UDF, even we use WITH SCHEMABINDING option, and USERDATAACCESS = 0, it�s still a parallel plan blocker.10 votes -
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.
-
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 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
- Don't see your idea?