軟體下載 SQL Server Management Studio 19.0

• 1

  版本確認

• 2

  檔案準備中

• 3

  檔案下載

What's new in this version:

- SSMS 19.0 is the first release that is fully aware of SQL Server 2022 (compatibility level 160)
- The installation of SSMS installs Azure Data Studio 1.41
- Improved keyboard navigation and screen reader text in the data classification window
- Added the ability to explicitly configure an attestation protocol in the "Connect To Server" dialog when using Always Encrypted with secure enclaves (column encryption)
- Connections to relational SQL instances now support Azure Active Directory Service Principal, Azure Active Directory Managed Identity and Azure Active Directory Default authentication methods. “Default” uses a series of possible sources for authentication, including environment variables, Azure Managed Identity, the user’s shared token cache, Visual Studio, Azure CLI, and Azure PowerShell. For more information, visit: Options (Azure Services
- Added support for SQL 2022 actions
- Changed to Microsoft.Data.SqlClient
- Added support for Contained Always On Availability Groups
- Improvements to Data Classification user interface
- Added support for increased nonclustered index size (up to 1700 bytes), originally made available in SQL Server 2016, to allow for expanded index recommendations
- Added a new page, Tools > Options > Output Window, to allow users to control what window channels appear in the Output window. See [Options Output Window - General) for more information
- Removed references to Azure Germany from SSMS
- Added support for import/export of a bacpac or dacpac created from a database with LEDGER = ON
- Added support for Ledger feature Database ledger. For more information, visit What is the database ledger?
- Introduced rollback support if selected tasks fail in the MI Link wizard
- The Maintenance Plan node is now available in Object Explorer
- Dropped Columns folder now exists under the Columns folder for Ledger tables, which have been altered to remove one or more columns
- Removed “Generate PowerShell Script from In-Memory OLTP Migration
- Improved checks for open connections
- Added ellipses button to Residual property for Merge Join operator. See SSMS: Add ellipsis button to Residual property for Merge Join operator
- Added option in Tools > Options > Query Execution to not display the “querying transaction count” window when closing a query window. See SSMS - Querying transaction count - Async
- Updated user interface for improved accessibility
- Added support for permissions introduced in SQL Server 2022 and SQL Server 2019
- Compatibility level defaults to 160 when scripting
- The showplan XML schema has been updated
- Added support for Hyperscale Optimized Query Processing
- Added DOPFeedbackAdjusted query plan attribute
- Removed dependency on SQL Server Native Client (SNAC/SQLNCLI) from SSMS. Visit Support Policies - SQL Server Native Client for more information
- Added support for the TRIM function

Fixed:
- Fixed accessibility issue when navigating in the data classification window
- Fixed issue where SSMS terminated unexpectedly when viewing a query plan from Activity Monitor
- Connection to Analysis Services is now available
- Addressed issue where users couldn't sign in to the Column Master Key dialog after signing out
- Fixed the issue when connecting to the Availability Group Dashboard for an AG on SQL Server 2016, which resulted in "unknown property ClusterType" error
- Added ability to create a NUL backup device against SQL Server 2017
- Provided ability to view SQL ERRORLOGs from Central Management Servers before SQL 2022
- Increased width of Column Master Key name in the rotation dialog, so the full name is visible
- Fixed an issue with authentication that doesn't use Azure Resource Manager and Microsoft Information Protection
- Addressed issue with logging into Azure with a non-SQL authenticated on a machine not joined to a domain
- Fixed the log provider type error, which occurred when copying a database using The SQL Management Object method
- Resolved error generated when restoring a backup to an existing database. See Unexpected behavior by SSMS
- Added ability to ignore unexpected elements in showplan XML when generating recommendations
- Resolved failure to populate the tuning log table issue
- Implemented security fixes, including replacing ZeroMemory with SecureZeroMemory
- Restored ability to deploy an extracted dacpac to a database via the Deploy Data-Tier Application option
- Fixed problem with leaking connections in MI Link
- Updated size of subscription dropdown in the login to Azure pane to properly display subscription names
- Updated display to show Azure sign-in options correctly
- Improved icon display when viewing Microsoft Information Protection in older versions of SQL Server
- SSMS no longer crashes using the Create View UX to create a view with invalid syntax
- No longer display Ledger objects if not supported by the platform
- Added support for Azure SQL Managed Instance partitioned tables in the Manage Partition Window UX
- Added ability to connect to a Power BI Datamart
- Fixed issue with audible notification occurring when closing a query window. See SSMS 18.11.1 Beeps When I Close a Query Window
- Fixed connection issue for a multi-server query with multiple registered servers in the same folder
- Fixed error "Merge publications can't be created from this database until the compatibility level is set to 70 or higher." when using the publication wizard to create a new merge publication
- Added missing database permissions
- Added ability to Script as Insert for DW
- The Queued status is now shown for queued jobs in SQL Agent
- Addressed CREATE TABLE scripting failure after adding datetime masking for a column
- Fixed incorrect syntax for DATE_BUCKET function
- Added missing options for CREATE USER and CREATE LOGIN
- The "Schedule..." menu item is now visible in the Azure SSIS Catalog
- Created consistent naming for Synapse offerings in SSMS
- Fixed an issue where reading target data for event sessions whose name overlaps with another session name caused data from the incorrect event session to appear in the viewer