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 18.1 Crashes when Opening a Database Diagram
SSMS 18.1 crashes (and restarts) when opening a database diagram without any error message.
I have created several diagrams from scratch thinking it might have to do with old formatting, but this does not appear to be the case.
You can edit a diagram (adding dozens of tables) with no problem. It is the opening of the diagram that results in the crash.
Latest bits for SSMS and SQL Server 2017 installed today.
SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET…1,238 votesThe fix for database diagrams was included in SSMS 18.6. For more information, please see https://cloudblogs.microsoft.com/sqlserver/2020/07/22/sql-server-management-studio-18-6-is-now-generally-available/.
Diagrams corrupted by previous versions of SSMS will open as a blank screen in SSMS 18.6+.
Drew
-
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/
-
SSMS 18.0 redraw issues when switching between multiple query windows
SSMS 18.0 redraw issues when switching between multiple query windows
Repro:
1. Open SSMS
2. Open a new query window and enter and execute a command, such as:SELECT @@SPID;- Open a second query window
- Using your mouse, switch back and forth between the two open query windows by clicking on their tabs.
- After several clicks (five to ten?), the content of the first window (query and result pane) may appear to be displayed in the second window, but you can't interact with any of the text.
- Switching back and forth a few more times may clear up the issue…
347 votesThis issue was fixed (or better, mitigated) in SSMS 18.5
As you can see, SSMS will automatically prevent the Visual Studio Shell from using the h/w acceleration.
While I hear that for some of you this workaround did not help, it seems that for the vast majority of the people here it was beneficial, so the workaround has been baked into SSMS 18.5.
Thanks,
-Matteo -
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?
187 votesAs of VS2019, there is no standalone installer for SSDT and the individual Analysis Services and Reporting Services, Integration Services components are available in the VS marketplace as extensions.
For more information:
https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt#changes-in-ssdt-for-visual-studio-2019Product announcement:
https://techcommunity.microsoft.com/t5/sql-server-integration-services/new-delivery-model-for-sql-server-data-tools-in-visual-studio/ba-p/479289 -
SSMS Crash when dragging table from Object explorer into new query window
Have just installed this version v18.1 and everytime I drag a table from Object explorer into new query window SSMS crashes, I have to kill it.
I have no add-ins installed, have rebooted since installing.O/s Win 10 15063.1387
129 votesThis has been fixes. Please try the latest version of SSMS – 18.5 and let us know if you are still seeing this issue.
thanks
Dinakar -
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 -
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.
96 votesThis was fixed in VS 2017 15.9.13:
https://docs.microsoft.com/en-gb/visualstudio/releasenotes/vs2017-relnotes#-visual-studio-2017-version-15913thank you,
Drew
-
Database Diagrams
Please add Database Diagrams back in SQL SERVER Management Studio
66 votesThis was completed in SSMS 18.1.
Caveat: there is still a known issue where diagrams created from SSMS on machine A opened with SSMS running on machine B would cause SSMS to crash.
This has been reported already and it is being investigated (it is just not as simple as I would like to be).
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.
-
SSMS 18.0 tabs don't display proper contents
I'm getting this CONSTANTLY on my new install of SSMS 18.0, and it's DANGEROUS. I'll open several tabs, and when I switch from one tab to another, the contents of the window don't change... I'm still looking at the old tab's contents with the new tab selected. It doesn't ALWAYS happen, but it happens at least half the time... FREQUENTLY. Further, I can close a tab, and the contents of the closed tab will still display under the new "top most" tab. This can lead to making changes to the wrong file, or being confused, and losing code. This is…
55 votesRendering issues in SQL Server Management Studio are associated with conflicts with graphics drivers. If you experience this behavior, be sure to uncheck “Use hardware graphics acceleration if available” in Tools>Options.
https://docs.microsoft.com/en-us/sql/ssms/the-sql-server-management-studio-environment
-
The Scalar Expression function would speed performance while keeping the benefits of functions.
SQL Server scalar User-Defined Functions (UDFs) have a performance problem that could be solved with an enhancement to the SQL Server database engine. Because SQL Server must execute each function on every row, using any function incurs a cursor like performance penalty.� However, since many UDFs are simple, they can often be converted to a single expression.� This suggestion proposes that a new type of UDF, the Scalar Expression UDF, be added to SQL Server.� Doing so would often eliminate the performance penalty paid when using scalar UDFs and allow them to be used more widely.� Using UDFs has the…
47 votesT-SQL UDF Inlining Delivered. Hopefully this covers most of the need
-
SSMS 18.0 GA can't be installed
When I'm trying to install SSMS 18.0 GA, I get error: "SSMS can only be upgraded by installing the package of the matching language. Please, use the matching version of the installer, or uninstall the current version of SSMS and run SSMS setup again." And I'm not alone: https://social.technet.microsoft.com/Forums/en-US/16d0e279-6ff4-4d5f-ad0a-5039235f03b9/ssms-2018-setup-blocked?forum=sqltools
45 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…
41 votes -
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 18.2 default language display bug
Hi, SSMS 18.2 displays the default language for all logins as Arabic, and my default language is us_english.
I'm using language 1033 so this shouldn't display as Arabic. I tried with a few servers - all the same. This is across all versions of the database engine from 2008, 2012, 2014, 2017 etc.
querying sys.server_principals shows this isn't actually the case so this seems to be display bug in SSMS 18.2
39 votesThis issue was fixed in SSMS 18.3.1
Thanks,
-Matteo -
SSMS: Freeze Column Headers When Scrolling
It would be nice if we could "freeze" column headers in SSMS like in Excel, so it's a little easier to remember where we are in larger result sets, and get helpful screenshots of data.
38 votesThis should be available already,.
thanks
Dinakar -
Removing dependency of MDS on SilverLight.
Removing dependency of MDS on SilverLight.
This dependency is preventing MDS from being used outside of POCs.35 votesAddressed as of SQL Server 2019
-
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 -
Restore CTRL-D shortcut for ResultsToGrid in SSMS
In SSMS 18 Preview 4, the default binding have changed to Edit.Duplicate lines, quoting https://feedback.azure.com/forums/908035-sql-server/suggestions/32896594 as a the motivation.
CTRL-D has been bound to ResultsToGrid, for almost 20 twenty years (that is since Query Analzyer came out in SQL 7.) That is engraved in many people's minds.
Yes, I can change the key binding, but so can people who prefer to use it to duplicate lines.
Please restore the original default. It does not serve the community to change existing bindings.
30 votes
- Don't see your idea?