Download Azure Data Studio and review the Release Notes to get started.

Note: If you are currently using the preview version, SQL Operations Studio, and would like to retain your settings when upgrading to the latest version, please follow these instructions. After downloading Azure Data Studio, click “Yes” to enable preview features so that you can use extensions.

Azure Data Studio is a new cross-platform desktop environment for data professionals using the family of on-premise and cloud data platforms on Windows, MacOS, and Linux. To learn more, visit our GitHub.

Azure Data Studio was announced Generally Available at Microsoft Ignite 2018. If you missed it, you can view that GA announcement here. You won’t want to miss the great orthogonality matrix that compares SQL Server Management Studio (SSMS) and Azure Data Studio, and it may provide answers to many of your questions.

Check out the video below for a general overview of Azure Data Studio.

The key highlights for the January release include:

• Azure Active Directory Authentication support
• Announcing Data-Tier Application Wizard support
• Announcing IDERA SQL DM Performance Insights (Preview)
• Updates to the SQL Server 2019 Preview extension
• SQL Server Profiler improvements
• Preview: results streaming for large queries
• User setup installation support
• Bug fixes

For a complete list of updates, refer to the Release Notes.

Azure Active Directory Authentication support

When Azure Data Studio was announced for Public Preview in November 2017, we received many requests and upvotes for features users wanted to see in Azure Data Studio. What turned out to be the third most upvoted feature request was Azure Active Directory (AAD) support, and we are excited to announce that AAD is now supported in Azure Data Studio.

Thanks to feedback from our user community from testing our insider builds, we have made it easier for you to connect with AAD. To see AAD in action, view the gif below.

For Azure SQL Database and SQL Data Warehouse users who require AAD, you can now get started with using Azure Data Studio. We challenge you to make a connection with AAD and try our Quickstarts for Azure SQL Database and Azure SQL Data Warehouse. If there are feature gaps, you can file an issue on our Issues page.

With the release of AAD, we made it a priority to release this feature as soon as dependencies in .NET Core were available. Thank you to our user community for helping us prioritize this feature through Twitter, GitHub, sqlcommunity Slack channel, and at conferences for this feature.

A more immediate way to let us know the importance of your feature request is to look for an existing issue on this list and encourage your coworkers, colleagues, and friends on social media to give a thumbs up on the issue, or blog about it. Even better—comment about what scenarios this feature would help you with. If a feature request doesn’t already exist, feel free to make it yourself. We want you to be part of the journey for this product.

Announcing Data-Tier Application Wizard support

Speaking of top customer feature requests, we have also added preview support for the Data-Tier Application Wizard used in SSMS, which is currently among the top 10 most requested features.

These wizards make it easier for users to manage .dacpac and .bacpac files, which simplifies the development, deployment, and management of data-tier elements that support an application. To learn more about using Data-tier applications, you can read this documentation.

The current experience combines the four separate wizards from SSMS into one wizard where users can choose which action they need to take. These actions include:

• Deploying .dacpac to SQL Server instance
• Extracting SQL Server instance to a .dacpac
• Creating a database from .bacpac
• Exporting schema and data to .bacpac

You can see Extract in action in the gif below.

In order to use this wizard, you will need to install the SQL Server Import extension. This is included with the Import Flat File Wizard, which is also a preview experience. This extension gives you the top two most used wizards from SSMS.

After downloading the extension, you can access the wizard in two ways:

• Right click a database in the Object Explorer and click Data-tier Application wizard
• If you are connected to a SQL Server instance, you can also start the wizard from the command palette (Ctrl+Shift+P) by searching for Data-tier Application wizard

As we did for SQL Server Agent and Import, we are actively seeking community feedback on improving this experience.

If you are interested in having a chat about this experience to help out your team, feel free to reach out on GitHub or email yu.alan@microsoft.com.

Introducing the IDERA extension SQL DM Performance Insights (Preview) extension

As part of the roadmap for Azure Data Studio, we’re finding ways to empower our partners to build extensions with our extensibility model. To show the progress we’re making on our extensibility, we are excited to announce the new IDERA extension.

IDERA SQL DM Performance Insights is an Azure Data Studio (ADS) extension that will display key performance metrics for SQL Server that have been collected and stored in a database repository by IDERA’s SQL Diagnostic Manager, a powerful performance monitoring, alerting, and diagnostics solution for SQL Server that proactively notifies administrators to health, performance, or availability problems via a desktop console, web console add-on, or mobile device.

This extension is a free add-in for Azure Data Studio that quickly allows you to see high level aggregated performance issues across multiple servers monitored by SQL Diagnostic Manager.

This preview provides the following features:

• Servers: Display metrics such as CPU, Disk I/O, network, and memory used
• Sessions: Display session summary averages such as client connections, logins, user processes, transactions, and oldest open transactions
• Databases: Display database summary-related statistics such as reads, writes, transactions, and log activity at the server level, as well as database statistical averages at the database level
• Queries: Display wait statistics and summaries of query statistics

This extension is free and will be supported through the IDERA Community Free Tools.

With partners joining our marketplace, if you are also interested in joining our extension marketplace or are curious about how to get started, feel free to contact me at yu.alan@microsoft.com to get started.

SQL Server 2019 Preview extension

Since announcing the Public Preview of SQL Server 2019 at Ignite, we are continuing to make updates to the SQL Server 2019 extension in Azure Data Studio, including improvements in the Azure Data Studio Notebooks and the Create External Data Wizard.

Azure Data Studio Notebooks

• The Notebook view UI has moved into Azure Data Studio core. This improves performance when loading and updating a notebook, including Jupyter notebook compatibility.
• The PROSE python package has been updated to 1.2.1 and includes a number of bug fixes. Use the Reinstall Notebook Dependencies command in the command palette to update this package.
• Cells have a simpler look with just one Run Cell button on the action bar, a real context menu with additional actions on the right of the cell. You can also double-click to edit support on Markdown cells.
• A Notebook API is in progress. This is included in the proposed API file for Azure Data Studio. As this feature is in active development, we expect some APIs to change, but these can be used to perform basic operations on a Notebook – Open New/Existing Notebook, query contents, add cells, etc.

Create External Data Wizard

• A new wizard to create external data sources from HDFS files/folders in SQL Server 2019 big data clusters has been added.
• Support for mapping SQL Server and Oracle Views has been added to the existing Create External Data wizard.
• Performance and reliability fixes for the existing wizard were also added.

Follow these instructions to download the extension and view the release notes.

SQL Server Profiler Improvements

We know the user community has been asking for a better Profiler experience. While working with Julie Lerman on her MSDN magazine article, we decided to make some investments to improve the Profiler experience.

To access SQL Server Profiler, you will need to download the extension through the Extensions marketplace. You can then right-click your target server and click Launch Profiler.

In this release, we fixed 11 bugs which include:

• Consistent Text/Details pane to pop up
• Fixed long time for profiler to refresh events
• Fixed Profiler for Azure SQL instances

We also added UI updates to the toolbar to make each action or dropdown clearer that the user can change. Please let us know any feedback you have.

In addition, we worked on improving the first-time experience to make it easier to launch Profiler. When you right-click a server and click Profiler, there is a default session name provided for each session template.

When you click start, Profiler will immediately start running. If you have any issues running Profiler, please let us know on GitHub.

Preview: Results streaming for large queries

In previous versions of Azure Data Studio, when a user ran large queries, no results would appear in the results grid until the query could show all of the results. This was not a great experience for our users, thus we did some investigating to improve this experience. In the latest build of Azure Data Studio, users can now see results streamed in the results grid. This makes it a better experience since users can see the results quicker and interact with their data instead of being in a waiting state.

However, this is still a preview feature so it is disabled by default. To enable this feature when you are running large queries, you will need to go to File > Preferences > Settings, and Search Settings for “sql.results.streaming” and set this value to true. Then you will need to restart Azure Data Studio.

Please let us know of any feedback you have for this experience, we will continue to be making investments in improving Query Editor and the results grid in the upcoming months.

User Setup installation support

Now featured on the Azure Data Studio download page is user setup installation for Windows only. This downloads the whole executable for Azure Data Studio so you won’t need admin privileges to install Azure Data Studio since the location will be under Local AppData folder. This also makes it easier to get monthly auto-updates.

We encourage users to download User Setup going forward. If you are transitioning from System Setup to User Setup, you will not lose any of your settings or extensions in the process.

Bug fixes and thank yous

If you would like to help make Azure Data Studio a great product, please share any feedback or report issues through our Issues page. Our engineering team is regularly monitoring the untriaged issues and assigning issues into different monthly milestones so that you will know we are working on it. Your votes on issues helps us prioritize.

To see the full list of bug fixes in the January release, view them here.

We also want to take this time to thank many of our users who have submitted PR’s or taken time to give us feedback in calls.

• Tarig0 for Add Routine_Type to CreateStoredProc fixes #3257 (#3286)
• oltruong for typo fix #3025′
• Thomas-S-B for Removed unnecessary IErrorDetectionStrategy #749
• Thomas-S-B for Simplified code #750
• Julie Lerman for feedback on Profiler and Import Wizard extensions, as well as writing MSDN magazine article on Azure Data Studio
• Dave Dustin for testing AAD, user setup, Data-Tier Application Wizard
• Peter Schott for feedback on AAD and Data-Tier Application Wizard
• Josh Booker for feedback on Data-Tier Application Wizard
• Constantine Kokkinos for feedback on Profiler
• Warwick Rudd for feedback on SQL Agent
• Mario Ezra for testing user setup

Contact us

If you have any feature requests or issues, please submit them to our Github issues page. For any questions, feel free to comment below or tweet us @AzureDataStudio.

The post The January release of Azure Data Studio appeared first on Microsoft SQL Server Blog.

Download Azure Data Studio and review the Release Notes to get started.

Note: If you are currently using the preview version, SQL Operations Studio, and would like to retain your settings when you upgrade to the latest version, follow these instructions. When you download Azure Data Studio, remember to enable preview features by default on first launch, and then you can disable in settings if you don’t need it otherwise you will be missing preview experiences like Query Plans, certain extension support, and more.

Azure Data Studio is a new cross-platform desktop environment for data professionals using the family of on-premises and cloud data platforms on Windows, MacOS, and Linux. To learn more, visit our GitHub.

Azure Data Studio was announced Generally Available last month at Microsoft Ignite. If you missed the GA announcement, you can see “Azure Data Studio for SQL Server” on the SQL Server blog. You won’t want to miss the great orthogonality matrix included comparing SSMS and Azure Data Studio and answers to many of your questions.

Check out this video for a general overview of Azure Data Studio.

In the October’s version of the monthly release blog, we will be covering features shipped in the September GA release as well as what is new in the October release.

This includes:

• Announcing the SQL Server 2019 Preview extension
  • Support for SQL Server 2019 features including big data cluster support
  • Azure Data Studio Notebooks
  • SQL Server Polybase Create External Table Wizard
• Azure Resource Explorer
  • The Azure Resource Explorer view lets you browse data-related endpoints for your Azure accounts and create connections to them in Object Explorer. In this release Azure SQL Databases and servers are supported.
• SQL Server Agent Extension improvements
• Improve Object Explorer and Query Editor connectivity robustness
• Added Connection name option to provide an alternative display name in the Servers view-let
• VS Code source code refresh from 1.23 to 1.26.1 with Grid Layout and Improved Settings Editor (Preview)
• Thank you to contributors

For complete updates, refer to the Release Notes.

SQL Server 2019 Preview extension

As announced at Microsoft Ignite, one of the most exciting extensions to share in our September GA release was the release of the SQL Server 2019 Preview extension. If you were following the blog announcements, starting with SQL Server 2019 preview, SQL Server big data clusters allow you to deploy scalable clusters of SQL Server, Spark, and HDFS Docker containers running on Kubernetes.

These components are running side by side to enable you to read, write, and process big data from Transact-SQL or Spark. SQL Server big data clusters allow you to easily combine and analyze your high-value relational data with high-volume big data. To learn about all the excitement of SQL Server Big Data Clusters, follow the documentation here.

These experiences are built as an extension to Azure Data Studio. We can go into full depth about all the great capabilities this extension includes, but deep-diving into any one of these features can be a full blog post itself. Here is a high-level summary of these features, and then you can see a full demo of the features below.

• Support for SQL Server 2019 features including big data cluster support
  • Connect to the HDFS/Spark Gateway shipped with SQL Server 2019
  • Browse HDFS, upload files, save files, and launch useful actions such as Analyze in Notebook for CSV files
  • Submit Spark jobs from the dashboard or right-click on a HDFS/Spark connection in Object Explorer
• Azure Data Studio Notebooks
  • Create or open Notebooks using an integrated Notebook viewer. In this release the Notebook viewer supports connecting to local kernels and the SQL Server 2019 big data cluster only.
  • Use the PROSE Code Accelerator libraries in your Notebook to learn file format and data types for fast data preparation.
• SQL Server Polybase Create External Table Wizard
  • Create an external table and its supporting metadata structures with an easy to use wizard. In this release, remote SQL Server and Oracle servers are supported.

Demo of SQL Server 2019 preview extension capabilities:

To download the extension, follow the instructions here.

Introducing the Azure Resource Explorer

As part of our goal to unify data management experiences, we have made it easier to manage your Azure subscriptions through the Azure Resource Explorer. Originally shipped as an extension, this feature is now built into the core product of Azure Data Studio.

After downloading the latest version, you will now see an Azure icon on the left bar, which you can click on to navigate to the Azure Resource Explorer.

With this feature, you can now manage your Azure SQL Server, Azure SQL Database, and the recently GA’ed Azure SQL Managed Instance resources easily. By clicking the filter icon to the right of the explorer, you can select which subscriptions you want to have displayed.

After drilling down to your target SQL instance through the explorer, you can then click on the plug icon next to each SQL instance to open up the connection dialog to directly connect to that resource and instantly start querying.

To learn more about the Azure Resource Explorer, check out our documentation.

SQL Server Agent extension improvements

One of our engineering focuses is to improve our first party extensions, which include SQL Server Agent, SQL Server Profiler, and SQL Server Import. As one of the first steps, we have brought a lot of UI and functionality fixes in SQL Server Agent, particularly in the Edit Job experience.

Now you can edit your Job steps, schedules, alerts, and notifications within the dialog.

If you are an avid user of SQL Server Agent, this is your chance to have a say in the new Agent experience in Azure Data Studio. You can report an issue directly on GitHub or go to Help->Report an issue to report directly from the product. Let us know your daily scenarios and how we can help empower you to use SQL Agent on Azure Data Studio daily.

To learn more about SQL Agent or how to acquire the extension, check out our documentation.

Improve Object Explorer and Query Editor connectivity robustness

As part of addressing customer reported issues, we put an emphasis on improving connectivity robustness across Object Explorer and Query Editor. In particular, queries that lose a connection will automatically attempt to reconnect.

To see a full list of the connection investments, see below:

• Load properties used for OE node status by group instead of individually
• Clear OE node error message when populating children
• Reopen connections prior to creating query execution data readers
• Fix OE and Binding Queue reliability bugs

Custom connection name option to provide alternative name

As requested on our GitHub issues page, you can now provide friendly connection names for your connections. This is particularly useful if your connection instance is an ip address, very long, or want to hide the name of the server in a public facing demo or docs.

This shows up as the last input box in the connection dialog as you can see in the screenshot below:

This will then appear in your Servers pane.

VS Code refresh from 1.23 to 1.26.1

Since Azure Data Studio forks from Visual Studio Code, our team continues to periodically “refresh” Azure Data Studio with stable and mature VS Code releases. This directly benefits users especially in editor and configuration experience.

The latest refresh picks up the latest changes from the July release of Visual Studio Code. This was implemented in the September release, but is still good to highlight for those coming from SQL Operations Studio.

A summary of changes:

• Preview support of improved settings editor
• Small UI changes in grid editor

To see the full list of changes, you can view the updates at the Visual Studio Code updates page. Be sure to view the changes in also the May and June changes.

Thank you to contributors

If you would like to help make Azure Data Studio a great product, share any feedback or report issues through our Issues page. Our engineering team is regularly going through the untriaged issues and assigning issues into different monthly milestones so that you can know we are working on it. Your votes on issues helps us prioritize.

In addition to submitting issues, users can also contribute by submitting pull requests for potential quick fixes, and we welcome those submissions. Here is a shout-out to some of the customers who have submitted PR’s that have been included in the product:

• AlexFsmn Feature: Ability to add connection name (#2332)
• AlexFsmn Disabled connection name input when connecting to a server. (#2566)
• philoushka for center the icon (#2760)
• anthonypants for Typo (#2775)
• kstolte for Fix Invalid Configuration in Launch.json (#2789)
• kstolte for Fixing a reference to SQL Ops Studio (#2788)

Contact us

If you have any feature requests or issues, please submit to our Github issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us @AzureDataStudio.

The post The October release of Azure Data Studio is now available appeared first on Microsoft SQL Server Blog.

We are excited to announce the August release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our GitHub.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this August release is the ninth major update since the announcement. If you missed it, the July release announcement is available here.

Highlights for this release include the following.

• Announcing the SQL Server Import extension
• SQL Server Profiler Session management
• New community extension: First responder kit
• Quality of Life improvements: Connection strings
• Bug bash galore

For complete updates, refer to the Release Notes.

Announcing the SQL Server Import extension

It all started from a simple idea: Take the #1 most used wizard in SSMS in the past year and bring this wizard to SQL Operations Studio. When we first released our Wizard and Dialog extensibility API’s in June, this was the perfect candidate to test our wizards and highlight to the community that these UI components are ready to incorporate in community extensions.

To provide some background, the Import Flat File Wizard was first released and announced on October 2017 in SSMS 17.3 (shameless plug alert: coincidentally my first SQL Server blog post and first project at Microsoft.) Outside of featuring in a Channel9 video, the wizard did not receive any additional marketing. Fast forward a few months, and it was suddenly the #1 most used wizard in SSMS. How did this happen?

A very common scenario for SQL Server users is that they simply want to take a .txt or .csv file and import it to their SQL database as a table. As much as we love the ever reliable Import and Export Wizard, for users unfamiliar with the wizard, there were many configuration options that can make first experience difficult. If a user simply wants to import a text file, how can we make a simple scenario easier? By creating a whole new wizard of course!

The Import Flat File Wizard utilizes a Microsoft Research framework known as Program Synthesis using Examples (PROSE) to import .txt and .csv files into a SQL table. It is a powerful framework for data wrangling, and it is the same technology that powers Flash Fill in Microsoft Excel and featured in many publications and demos led by Sumit Gulwani. This technology turns the Import Flat File experience into a 6 click experience to go from selecting a file and importing into your database. Clearly, incorporating PROSE into everyday database tasks is a delighter for our users, and we will continue to put investment into creating experiences with PROSE.

Logically, it made perfect sense to have an AI-powered feature be our first wizard experience in SQL Operations Studio, but our engineers were at full capacity, so we had to be a little creative to make this possible.

Every year since Satya Nadella became CEO, Microsoft holds a global, company-wide hackathon where employees spend 3 days working on any project ranging from Hack for Good projects, VP-sponsored challenges, or from a random idea on the drive back home. This was the perfect opportunity to pitch bringing the Import Flat File Wizard to SQL Operations Studio, while also promoting cross-platform and open source development to our fellow co-workers.

By the time of the Hackathon, we had 4 interns and 7 full-time employees signed up for the project. More importantly, we asked why external team members chose our project, and we were blown away by the passion the interns and external team members had for SQL Server, and how they wanted to work on projects to improve SQL Server user experience.

Starting from mockups featured on PowerPoint slides, we shared the vision of the project while quickly onboarding new team members to our tech stack. It was not the most productive first day, but we did end up finding our rhythm. Using this momentum, we iterated quickly and were nailing our checkpoint sync-ups throughout the day, but there was still a lot to get done. However, with one hour to go before the Hackathon tents closed, we completed the first SQL Server Import experience in SQL Operations Studio end-to-end. Very proud of this team for getting a shippable deliverable within the allocated Hackathon time.

Our intern, Amir Omidi, worked on the fit and finish for the wizard for the remainder of his internship, and we are grateful for his hard work.

Now, we are ready to share this extension with the community. You can get this extension from the Extensions Manager. This feature not only brings the same simplicity as the SSMS wizard, but also brings this experience cross-platform to our macOS and Linux users. You can start the wizard with the same right click experience or press Ctrl + I.

Overall, this project taught us several things:

• Our SQL Server users love AI-assisted features, and this is the first of many AI experiences in SQL Operations Studio.
• Interns are very talented. Invest in their growth.
• Keep things simple. Bring our users with us on our journey.

If you have ideas of what you would like to see in this extension, let us know through our community feedback. We look forward to bringing more PROSE experiences into SQL Operations Studio in the future.

SQL Server Profiler Session management

Since the June release, we have been making improvements with SQL Server Profiler. We are excited to announce the Profiler extension now supports session management. With session management, you can now configure your most popular sessions as you can in SSMS.

To try out this feature, you will need to make an active connection to a SQL Server instance. You can then launch Profiler by clicking on a server or database in the Object Explorer and pressing Alt + P.

This will pop up a New Session dialog as shown in the gif. Here you can give an easy to remember name like Profiler and hit create. If you don’t want to create a new profiler session, simply press Cancel.

To select the session you just created, simply click on the dropdown next to Start/Stop and select Profiler.

You can now start profiling your SQL Server events. Note that there is also a new Create button where you can pop up the Create Session dialog.

With template support released last month and session support in this release, we hope to continue to improve the Profiler extension for all the avid Profiler users in the SQL world. A big thank you to Madeline MacDonald for her hard work in shipping Profiler over the course of her internship.

New community extensions: First Responder Kit

Continuing our extensibility story, our marketplace now includes Brent Ozar’s First Responder Kit. For those unfamiliar with the First Responder Kit, this toolkit helps users understand why their SQL Server is down or slow. Specifically, there are five main scripts featured:

• sp_blitz: Overall health check
• sp_blitzcache: Most resource-intensive queries
• sp_blitzfirst: Why is server slow
• sp_blitzindex: Indexes missing or slow
• sp_blitzwho: Queries currently running

To leverage these features, you will first need an internet connection. Then, open the command palette with Ctrl+Shift+P and type > first responder kit: import to see a list of scripts to import. Then select the script with arrow keys and press enter.

Once the scripts are loaded to the database, you can run the scripts by again opening command palette and type > first responder kit: run to view the list of available scripts to run. Then select the script with arrow keys and press enter.

A big thank you to Drew Skwiers-Koballa for using our extensibility API’s to create a SQL Operations Studio extension. Also thank you to Brent Ozar Unlimited team for having these awesome scripts easily available for the community.

In addition to having a great new extension, Drew shared his story for creating a SQL Operations Studio extension through a detailed blog post. If you are interested in leveraging extensions API’s or have a great idea for an extension, we would highly recommend checking out his blog.

Drew also wanted to let the community know about his extension authorship experience:

“I want everyone to understand that in 1-2 hours you can go through an extension writing tutorial and start working on crafting your own solutions. The development platform is just as accessible as the application itself – Windows, Mac, and Linux. Building a SQL Operations Studio extension is a great way to be a data community contributor, especially for someone who might not be keen on giving talks or writing blog posts. I’m extremely excited for the future possibilities in SQL Operations Studio as more APIs are created each month.”

Quality of Life improvements: Connection Strings

As requested by the community, we have also made it easier for you to handle connection strings in SQL Operations Studio.

Generate Connection String

If you need to quickly generate a connection string, you can follow these three steps:

1. Open a query editor with an active connection.
2. Open Command Palette (Ctrl+Shift+P), and type Get Current Connection String and then press Enter.
3. Copy connection string from notification pop-up.

Note: Password will be removed from the returned string.

You can now use or share the connection string.

Populate info from Connection String

If you have a valid connection string such as from the Azure Portal, you can now copy your connection string and paste the string into the connection dialog and it will auto-populate the fields based on the connection string.

Bug bash galore

In addition to the new features, we dedicated time to fix many of the top user reported bugs.

To highlight high impact ones:

• Cursor position no longer loses context when switching between tabs #1744
• Script As now auto-connects to the server connection. #825
• .sql files now are associated with SQL Operations Studio #1836

All fixed customer reported issues:

• Parse SQL in a Query Editor window by using the Parse Syntax command
• Save edit data scroll position when switching tabs #2129
• View as Chart options are cut off at the bottom #1497
• Cancel change connection disconnects current connection #1474
• Bug: Error message when saving Excel file second (and subsequent) time #1748
• Update document icon for Dashboard and Profiler documents #2107
• SQL Tab DB Icon is red #387
• Added more saveAsCsv options #2099
• Feature Suggestion: Get Connection String for existing connection #1620
• Agent: Enabled button to import queries from sql files #2042
• Copy from query results grid is off by 1 column #1985
• Add VS Code version to About dialog #1998
• double-click not selecting @ in variable name #143
• Typing N” autocompletes to N”’ #1850
• Results Grid Row Indicator Zero Based #2152
• Fix the decimal separator #1317
• SelectBox doesn’t change color when disabled #1624
• Save as JSON/EXCEL/CSV not work #1728
• Shell/Dashboard: Main viewlet icons are draggable and can crash the app #1524
• Can’t use Ctrl+C shortcut to copy from result pane #2091
• Updating causes application icon to be removed/replaced in Windows #1285
• Not able to expand/collapse remote file browser folder by clicking name #1578
• sqlops.desktop [Desktop Entry] – redundant value for Name & Comment #1278
• Edit data: cell doesn’t revert to original value on hitting Escape key #1782

Contact us

If you have any feature requests or issues, please submit to our GitHub issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us @SQLOpsStudio.

The post The August release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

We are excited to announce the July release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS, and Linux. To learn more, visit our GitHub.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this June release is the eighth major update since the announcement. If you missed it, the June release announcement is available here.

Highlights for this release include the following.

• SQL Server Agent preview extension Job configuration support
• SQL Server Profiler preview extension Improvements
• Combine Scripts Extension
• Wizard and Dialog Extensibility
• Social content
• Fix GitHub Issues

For complete updates, refer to the Release Notes.

SQL Server Agent configuration

As part of our story of bringing over SSMS features and improving user experience, we are excited to introduce SQL Agent configuration support.

Summary of changes include:

• Added view of Alerts, Operators, and Proxies and icons on left pane
• Added dialogs for New Job, New Job Step, New Alert, and New Operator
• Added Delete Job, Delete Alert, and Delete Operator (right-click)
• Added Previous Runs visualization
• Added Filters for each column name

In addition to jobs, users can now view Alerts, Operators, and Proxies through the icons on the left pane as demonstrated in the gif above.

We also made several improvements for the Job View. Previous Runs visualization can now be seen so that a user can quickly see a job’s history of past runs if they passed or failed.

This release also made it easier to find specific jobs in a large list of jobs. Imagine you had a list of 100+ jobs and you only wanted to see the failed jobs? Now you can by checking out the gif below using the filter column option.

With all the improvements in Views, we have added new dialogs so that users can now add Jobs, Alerts, and Operators without having to go to SSMS. To open each dialog, click New Job above each respective view.

For all the SQL Agent enthusiasts out there, we would love for you to try out the new SQL Server Agent experience and let us know what you like and what is still missing for you to use Agent day to day. As part of doing our engineering out in the open, we need your feedback so that we can create experiences that empower you to do your job (pun intended).

To learn more about SQL Server Agent, check out the documentation.

SQL Server Profiler improvements

With the release of SQL Server Profiler extension last month, our team has been working hard on improvements, especially making launching Profiler quickly.

Summary of changes include:

• Added Hotkeys to quickly launch and start/stop Profiler
• Added 5 Default Templates to view Extended Events
• Added Server/Database connection name
• Added support for Azure SQL Database instances
• Added suggestion to exit Profiler when the tab is closed and Profiler is still running

As seen in this gif, you can quickly get Profiler open after making a server/database connection. With this release, we added Keyboard Shortcuts to Launch Profiler (Windows: Alt + P Mac: Ctrl+ALT+P) and Start/Stop Profiler (Windows: Alt + S Mac: Ctrl+ALT+S). From our user survey, the highest priority for users is to be able to start Profiling as quickly as possible. Now with two keyboard strokes, you can start Profiler.

In addition, Profiler now has added Default templates for five different views: Standard, TSQL, Tuning, TSQL_Locks, and TSQL_Duration. When you click on each one, a different list of columns will generate in your Profiler view so that you can focus on the areas that you are investigating. At the moment, it will reset the view each time.

In addition, each Profiler tab will show the server/database the Profiler instance is connected to. You can see the name in the top right of the above screenshot, which is localhost/Adventureworks2014.

Please let us know what you think and what you would like to see in Profiler.

Combine Scripts Extension

We have a new community extension published in our Extensions Manager. Created by Cobus Kruger, the Combine Scripts Extension for SQL Operations Studio is now available.

From the extension description: Ever needed to execute several scripts spread over several folders? Now you can select several files and folders, right click and click Combine Scripts, and generate a single combined file to execute or use any way you choose.

For those new to extensions, here are the instructions to access the Extensions Manager and download the Combine Scripts extension. For this extension, in particular, the install button will take you to a download link for the VSIX package. Download the VSIX, and then click File -> Install Extension from VSIX Package.

Dialog and Wizard extensibility

With this release, we are continuing to provide more opportunities for extension authors, which we highly encourage you to participate. The highlight for this release is we have now provided options for extension authors to incorporate Dialogs and Wizards in their extensions.

The differences between using dialogs and wizards are very similar to SSMS. Generally, use Wizards for step-by-step scenarios, and use dialogs for most other cases.

Extension authors can see the full list of Dialog and Wizard API’s.

To see this in action, check out our sample extension that includes this code.

We are excited to see what our extension authors can come up with these new extensibility points. If you aren’t an extension author but have ideas in mind, please feel free to share on Twitter or GitHub Issues.

Social content

Over the past month, we have seen a lot of great content about SQL Operations Studio as we monitored social media. We highly encourage the community that if you love this tool, consider using this tool in demos and blog posts. We will also make sure to share any of your content with the community through our Twitter handle (@sqlopsstudio).

If you would like to use SQL Operations Studio at sessions like SQL Saturdays or PASS Summit, feel free to reach out to our team and we can work with you. If there are any demo blockers, please submit an issue on our GitHub Issues. Our engineers will help unblock your scenarios.

With the launch of the Data Double-Click channel, our Principal PM Lead, Vicky Harp, discussed SQL Operations Studio with Scott Klein. Check out the conversation below.

In addition, Vicky was also interviewed by Joey D’Antoni for Redmond Mag, covering the current state of SQL Server Tools development.

SQL Ops Studio also had a presence at OSCON in Portland this year, where Shayne Boyer shared SQL Operations Studio and mssql-cli.

Fixed GitHub Issues

Here is a summary of issues addressed:

• #728 No response to Add Connection on macOS
• #1718 Unable to connect to any data source
• #1713 Number of rows affected
• #1843 Better Table organization
• #1612 Results grid text display is messed up by international characters
• #1749 BUG: HTML data in a column gets interpreted
• #1830 Setting iconPath in ButtonComponent after component() is called does not change icon
• #1789 Extensibility: if you add a connection provider uninstall will never remove it from the list
• #1799 Top 10 DB Size chart does not work on ccase-sensitive instances
• #1724 Extension dialogs have stopped working
• #1719 TypeError when Connecting to Server
• #1693 Backup dialog: File browser UI is broken
• #1817 Error de Ortografia
• #1791 Sqlops Extensions: queryeditor.connect() connects to the target database, but UI does not show the editor is connected
• #1814 d.ts typo causing implicit ‘any’ type definition

Contact us

If you have any feature requests or issues, please submit to our GitHub issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us.

The post The July release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

We are excited to announce the June release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our GitHub.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this June release is the seventh major update since the announcement. If you missed it, the May release announcement can be viewed here.

The June public preview release is focused on improving our Extensibility experience with the release of new extensions as well as addressing top GitHub issues.

Highlights for this build include the following.

• SQL Server Profiler for SQL Operations Studio Preview extension initial release
• Azure SQL Data Warehouse extension
• Edit Data Filtering and Sorting
• SQL Server Agent for SQL Operations Studio Preview extension enhancements for Jobs and Job History views
• Build your own SQL Ops Studio extension
• Visual Studio Code Refresh
• Fix GitHub Issues

For complete updates, refer to the Release Notes.

SQL Server Profiler for SQL Operations Studio Preview

The SQL Server Profiler for SQL Operations Studio Preview extension is now available in the Extension Manager. This is the initial preview release for a new lightweight XEvent-based profiler. The SQL Server Profiler extension makes it simple to quickly trace server activity for troubleshooting and monitoring.

If you want to try out the SQL Server Profiler extension, follow these instructions:

1. Install the extension from the Extensions Manager.
2. After you reload SQL Operations Studio, press Ctrl+Shift+P or open the Command Palette from the Gear icon on the bottom left.
3. Type ‘Profiler’ and press Enter on ‘Profiler: New Profiler’
4. Press start to see your Extended Events (view gif below)

We’ll continue to enhance this extension over the next couple releases. This is still a preview version and we would love to hear initial feedback from the community.

Shortly after this blog publishes, an issue will be opened in GitHub issues where we will share our design process for each screen for SQL Server Profiler. We welcome community input there as we work on improving SQL Server Profiler in SQL Operations Studio.

Azure SQL Data Warehouse Extension

Last month, the Azure SQL Data Warehouse team blogged on creating a customizable management experience with SQL Operations Studio. Instead of asking new users to manually add JSON snippets in Settings, we reached out to the DW team to see if they would be interested in building an extension to improve acquisition for users. After working with us on building a custom insight extension, the team is excited to announce the preview release of the Azure SQL Data Warehouse Extension! You can now seamlessly install the extension from the SQL Operations Studio Extensions Manager surfacing a pre-built dashboard for your data warehouse.

Once you install the extension, you simply make a connection to your SQL DW instance, view the server dashboard, and you can see the extension as a tab.

Insight widgets are generated by using T-SQL scripts embedded within SQL Operations Studio. All monitoring scripts are uploaded to the following GitHub repo: SQL Data Warehouse samples.

We are looking to improve this extension and would love to hear your feedback to improve this extension. Please feel free to contribute or provide feedback.

Edit data filtering and sorting

Edit data on a table opens the top 200 rows by default. To modify the query, click on the “Show SQL Pane” toolbar button to open the query pane. The query can be modified in the SQL editor pane to filter or sort the resultset. Check out the gif below to see this feature in action.

Build your own extension

In the last couple releases, you may have noticed how our Extensions Manager has grown with extensions created by Azure SQL Data Warehouse, Redgate, and community members. We want to continue to work with the community and our partners to create SQL Operations Studio extensions.

If you want to get started, you can learn to build a sample insight extension through our Extension Guide we created for Microsoft Build.

You can further learn how the SSMS keymap extension was created by following Kevin Cunnane’s blogs:

• Writing a SQL Operations Studio extension in 15 minutes
• Publishing an extension for SQL Operations Studio

Both the Extension Guide and Kevin’s blog posts use the generator-sqlops yeoman generator to help make it even easier to make an extension.

If any of these extensions in this generator interest you, feel free to try it out! If you are interested in hosting your extension in our Extensions Manager or would like help building an extension, feel free to reach out to the team on GitHub or email alayu@microsoft.com.

Our team also brought in Wizard and Dialog extensibility support, so feel free to reach out to us if you want to learn more and add wizards and dialogs to your extension. You can learn more here.

Want to learn more about our roadmap for extensions? Learn from our Microsoft build session if you missed it!

Visual Studio Code refresh

Since SQL Operations Studio forks from Visual Studio Code, our team periodically includes “refreshes” based on latest VS Code monthly releases. This usually brings nice features for the editor and configuration. The latest refresh picks up VS Code v1.23, which includes the March and April 2018 release.

• Easier way to open large files
• Syntax highlighting optimization
• Highlighted indent guides
• Column Selection using middle mouse button

For more information, check the VS Code release notes.

Fix GitHub issues

Here is a summary of issues addressed:

• #1204 Feature request: Please make the results grid auto-fit column width to data, and/or remember manual changes if the same query is re-run
• #1398 Should show add message and add account button when linked account is empty
• #1399 Linked account tab is broken when the view is collapsed
• #1374 SQL Tools Service crashes when opening .sql file from disk
• #1372 Missing SQL keyword “BETWEEN”
• #1395 ‘MATCH’ keyword crashes SQL Tools Service
• #1496 “New Profiler” context menu option in Object Explorer does nothing.
• #1495 Query editor “Explain” query plan is broken

Contact us

If you have any feature requests or issues, please submit to our GitHub issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us @SQLOpsStudio.

The post The June release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

This post is co-authored by Karl Burtram, Senior Software Engineer, SQL Server.  

We are excited to announce the May release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our Github.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this May release is the sixth major update since the announcement. If you missed it, you can view the April release announcement.

The May Public Preview release is focused on improving our Extensibility experience with the release of new extensions as well as addressing top Github issues.

Highlights for this build include the following.

• Announcing Redgate SQL Search extension available in Extension Manager
• Community Localization available for 10 languages: German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese and Traditional Chinese!
• GDPR-compliant build has reduced telemetry collection, improved opt-out experience and in-product links to Privacy Statement
• Extension Manager has improved Marketplace experience to easily discover community extensions
• SQL Agent extension Jobs and Job History view improvement
• Updates for whoisactive and Server Reports extensions
• Fix GitHub Issues

For complete updates, refer to the Release Notes.

Announcing Redgate SQL Search extension

Redgate SQL Search in SQL Operations Studio extension is now available for installation through the Extension Manager Marketplace! The SQL Search extension lets you find database objects across an active connection. The search results makes it simple to jump to the object in the Object Explorer or to view the object’s definition.

We definitely recommend installing this extension. As SQL Ops Studio evolves, we will rely heavily on extensions to provide core functionality, so we expect that most users will want to have several extensions installed for the best experience.

Startup Performance improvements

We want SQL Operations Studio to be fast and efficient to maximize user productivity. Reducing the time it takes to launch SQL Ops Studio is one of the key scenarios where we’ve been making continual investments. Fortunately, our upstream platform, Visual Studio Code, is also optimizing this same scenario. One key improvement we merged from VS Code’s February release was ASAR Node module bundling.

We use product telemetry from the Startup scenario to understand how long users are waiting for SQL Ops Studio to launch. This telemetry allowed us to confirm that the April Public Preview delivered approximately 30-40 percent startup time improvements for most users. Particularly users experiencing the slowest startups have seen the largest improvements.

The below chart shows startup times bucketed into key percentiles: 25, 50, 75, 90, 95, 98, 99 percent. At the risk of being pedantic, this would mean, for example, at the 50 percent bucket half the startups were faster than that time and half the startups were slower than that time.

Community Localization available

Community Localization resources for German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese and Traditional Chinese are available for the May Public Preview. We’ll continue working over the next couple months to get the product 100 percent localized.

We’d like to thank the translation community for helping to make SQL Operations Studio available to users in their preferred language!

The below screenshot shows an example using the Italian locale.

GDPR compliance

There are several updates in May Public Preview that were needed for GDPR compliance. Specifically, we reduced the telemetry being collected, improved the opt-out experience by adding a notification on first launch, and added a Privacy Statement item to the Help menu.

Extension Manager enhancements

The Extension Manager Recommended section has been replaced with a Marketplace section. The Marketplace will display all available extensions. Recommended extensions are sorted to the top.

Check out some of our 1st-party and community contributed extensions. And take a look at our Extensibility Getting Started page to see how easy it is to add your own extension to the marketplace!

Fix GitHub issues

Here is a summary of issues addressed:

• #703 Entering HTML-like text in edit data causes value to display incorrectly until refresh
• #821 sqlopsstudio.deb package dependency
• #1260 keyword ‘distinct’ not highlighted
• #1332 Edit data revert row doesn’t work
• #1215 SQL Agent extension and the status bar
• #1316 SQL Agent Don´t resize after change windows size
• Improve Manage Dashboard Properties scrolling

Contact us

If you have any feature requests or issues, please submit to our Github issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us @SQLOpsStudio.

The post The May release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

We are excited to announce the April release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our GitHub.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this April release is the fifth major update since the announcement. If you missed the March release announcement can be viewed here.

The April Public Preview release is focused on improving our Extensibility experience with the release of new extensions as well as addressing top Github issues.

Highlights for this build include the following.

• Public preview release of SQL Agent extension
• Added new extensions and improved existing extensions
  • Improvements to Server Reports Extension
  • Release of SSMS Keymap extension
  • Release of AlwaysOn Insights extension
  • Release of MSSQL Instance Insights
  • Release of MSSQL Db Insights
• Added Visual Studio Code 1.21 platform source code refresh
  • Improved large and protected file support for saving Admin protected and >256M files within SQL Ops Studio
  • Integrated Terminal splitting to work with multiple open terminals at once
  • Reduced installation on-disk file count footprint for faster installs and startup times
• Continue to fix GitHub issues

For complete updates, refer to the Release Notes.

Preview release of SQL Agent extension

Since SQL Operations Studio was released for public preview, one of the most requested features was providing SQL Agent support. Bringing over the most popular SSMS features has always been on our roadmap, but we wanted to make sure we did this the right way. For years, customers have submitted issues that were difficult to change due to being built on old dialog and wizard frameworks. With SQL Operations Studio, we had an opportunity to bring a modern user experience to our features while maintaining the same functionality that our users are experts with.

To make this possible, the engineering team reached out to the SQL Server community to learn more about your top scenarios and get direct feedback about our initial mock-ups. This involved creating surveys, scheduling user interviews, and promoting community discussion through a demo on Youtube showing our initial prototype. With your help and the release of Extensions Manager in the March release, we have provided you an initial preview release of SQL Agent.

When you install SQL Agent from the Extension Manager, you can view the SQL Agents extension as a tab on your server dashboard. To learn how to install an extension, please view this how-to guide.

This initial release focuses on providing a great View Jobs and Job History experience. You can see a list of all jobs including color-coded successful and filed jobs, names of jobs, and error messages. To see the job history of a specific job, you simply click on that job. This view lets you see a history of past runs, and also provides the ability run or stop the job.

The next step will be to add Job Configuration functionalities, including providing support for creating a job, setting alerts, and scheduling jobs. We would love to hear your feedback about this initial release through our GitHub Issues page and also any suggestions you may have as we build out Job Configuration.

This is the first step as we continue to bring over popular features to SQL Operations Studio from SSMS. Please continue to let us know what are your must-have features and feel free to join the discussion.

Adding and improving extensions

In the March Public Preview release, we first introduced the Extension Manager to SQL Operations Studio. With this release, we introduce 5 new extensions that you can now try out in the Extensions Manager (to get started, read the how-to install extension guide).

• SQL Agent is the extension to view and run SQL Agent jobs as described earlier.
• SSMS Keymap ports the most popular SSMS keyboard shortcuts to SQL Operations Studio. Created by Kevin Cunnane.
• AlwaysOn Insights is a collection of widgets designed to provide insights into AlwaysOn Availability Group components to assist DBA’s or similar in managing their environment. Created by Matt Lavery.
• MSSQL Instance Insights is a collection of widgets designed to provide insights into MSSQL Instance to further extend the built-in default widgets. Created by Matt Lavery.
• MSSQL Db Insights is a collection of widgets that are designed to provide insights into MSSQL Database to further extend the built-in default widgets. Created by Matt Lavery.

Over the past month, we have received a lot of emails and tweets from the community who were interested in creating their own extension. One of our engineers, Kevin Cunnane, wrote awesome blog posts that includes his process to create and publish the SSMS Keymap extension:

• How to write a SQL Operations Studio extension in 15 minutes
• How to publish an extension for SQL Operations Studio

For additional resources to get started writing an extension, please refer to our GitHub Extensibility Wiki Guide. Feel free to also reach out to @sqlopsstudio on Twitter if you need help getting started after checking out these resources.

In addition to adding new extensions, we also brought updates to existing extensions, especially Server Reports. These changes include:

• Fixed DB Space Usage where it threw an error when database names contain special characters
• Changed DB Space Usage and DB Buffer Usage to show only top 10 data
• Updated ReadMe to reference Paul Randal’s wait types library for more info about the Wait Counts widget

As we build out our extensibility story, we will continue to collaborate with the community to learn and improve the way we build and publish extensions. This is the way we envision bringing over SSMS features while also empowering the community to contribute and build their own extensions to share with the community.

Visual Studio Code Refresh

One of the most significant highlights of this release is the Visual Studio Code 1.21 platform source code refresh. Since we fork from VS Code, we do these periodic updates and also get feature improvements. The key highlights with this refresh specifically for SQL Operations Studio are:

• Improved large and protected file support for saving Admin protected and >256M files within SQL Ops Studio
• Integrated Terminal splitting to work with multiple open terminals at once
• Reduced installation on-disk file count footprint for faster installs and startup times

For additional details, checkout the Visual Studio Code February Release Notes, and the Visual Studio Code January Release Notes.

Fix GitHub issues

Fixing user-reported issues may not always get as much recognition as new feature releases, but it is definitely worth calling out. If we truly want to be a community driven tool, we will continue to work on addressing your submitted issues. Here is a summary of issues addressed:

• #37 When the chart viewer throws an error, unexpected behavior occurs.
• #462 Feature Request: Option for Server Groups to be expanded by default
• #1023 Add square brackets for ms_foreachdb call from flyfishingdba
• #1050 Clear insights view before showing error
• #1057 Restore and new query actions in explorer-widget are broken
• #1068 Dashboard Output windows pops-up with error message for Azure DB
• #1069 Connection Dialog shows Server Required error when initially displayed
• #1070 Server Groups now require a double-click to expand
• #1072 Select control background is semi-transparent
• #1115 Fix all high contrast accessibility issues in sqlops
• #1101 Extension fails to upgrade “Download Manually” link goes to wrong location
• #1103 V Scroll not working on Home Tab
• #1104 SQL extension tabs stopped working
• #967 Expect query plan when select XML showplan in the result grid
• #606 intellisense – Bad suggestion for ‘update’ command
• #1048 Pre-login SSL/TLS handshake error
• #1150 Various types of query charts throw exceptions and don’t render

Contributions and thank you

We would like to thank all our users who raised issues, and in particular the following users who helped contribute fixes:

• flyfishingdba for Add square brackets for ms_foreachdb call (#1023)

Contact us

If you have any feature requests or issues, please submit to our GitHub issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us @SQLOpsStudio.

The post The April release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

This post is co-authored by Karl Burtram, Senior Software Engineer, SQL Server. 

We are excited to announce the March release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our Github.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this March release is the fourth major update since the announcement. In case you missed it, you can view the February release announcement here.

Take a moment to breathe, this is a loaded update.

The March Public Preview release is focused on improving our Extensibility story and continuing to address top GitHub issues. This includes enabling Extension Manager, improving the Manage Dashboard experience and providing a couple Insights extensions. Please see the following details.

• Enhance the Manage Dashboard extensibility model to support tabbed Insights and Configuration panes
• Dashboard Insights extensions for sp_whoisactive from whoisactive.com and a Server Reports example
• Extension Manager enables simple acquisition of 1st-party and 3rd-party extensions
• Add additional Extensibility APIs for connection and objectexplorer management
• Community Localization open for 10 languages
• Continue to fix important customer impacting GitHub issues

For complete updates, refer to the Release Notes.

Extension Manager enables simple acquisition of 1st-party and 3rd-party extensions

The Extension Manager makes it easy to discover and acquire additional SQL Operations Studio functionality. We’ve adopted the in-product extension management experience from Visual Studio Code. For users unfamiliar with this UI it consists of the following components.

• ‘Marketplace’ of Recommend Extensions which can be easily discovered and installed
• List of Installed Extensions which can be disabled or uninstalled
• Extension Details page that displays the extensions readme content and other metadata

Extensibility is a key tenet of the SQL Operations Studio project roadmap. We plan to make available both 1st and 3rd features as extensions. We look forward to working with the community to build a rich tools ecosystem. Please contact us on Gitter if you’re interested in building an extension.

Note: If you don’t see the Extension Manager icon you may need to enable it by right-clicking on the left Activity Bar, and then click Extensions on the context menu.

Dashboard Insights extensions for sp_whoisactive from whoisactive.com

The March release introduces improved Manage Dashboard extensibility. Extensions can now provide tab panels to the dashboard to group related functionality. Check out the sp_whoisactive extension as a great example of using the dashboard insights extensibility points.

Here are some notes from the extension readme: Sp_whoisactive is a procedure written by Microsoft MVP Adam Machanic. It is a very useful tool for activity monitoring and troubleshooting.

Who is Active is a DMV-based monitoring stored procedure that uses 15 different views to show a large amount of data about what’s running on your server.

Who is Active was designed to be extremely flexible, and includes options to not only get different types of data, but also to change the output column list and sort order.

Check out the source code for the whoisactive extension and other extensibility samples.

Join the extensibility ecosystem

With these extensibility investments, we want to empower the community to build their own extensions and join our extensibility ecosystem. We strongly believe that our talented SQL Server community can build awesome extensions, and we have provided resources to help get you started:

• Check out Extensibility Getting Started Docs
• Utilize our SQL Operations Studio Extensibility API to interact with other application parts such as Object Explorer
• Leverage two extensions created by our engineering team (we strongly recommend using VSCode for development).
  • Use this Yeoman generator to help bootstrap your project.
  • Use this VSCode extension to help with your SQL Operations Studio debugging experience.

Community Localization Open

Recently, we announced SQL Operations Studio availability on the new Microsoft Community Localization platform. Localization is now opened for 10 languages: French, Italian, German, Spanish, Simplified Chinese, Traditional Chinese, Japanese, Korean, Russian, and Portuguese (Brazil). You can contribute to localization for both software and docs.

Contact us

If you have any feature requests or issues, please submit to our Github issues page. For any questions, feel free to comment below, message us on Gitter, or tweet us @SQLOpsStudio.

The post The March release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

We are excited to announce the February release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the Release Notes to get started.

SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB and SQL DW from Windows, macOS and Linux. To learn more, visit our GitHub.

SQL Operations Studio was announced for Public Preview on November 15th at Connect(), and this February release is the third major update since the announcement. If you missed it, the January release announcement is available here.

The February release includes several major repo updates and feature releases, including:

• Added Auto-Update Installation feature
• Added Connection Dialog ‘Database’ Drop-down
• Added functionality for new query tabs keeping active connection
• Fixed bugs in SQL Editor and auto-completion

For complete updates, refer to the Release Notes.

Auto-Update Installation

We want to use the February Insiders builds to test the auto-update feature. The 0.26.2 build will be released as an auto-update to 0.26.1 (assuming there are no issues that require publishing a new build to successfully support auto-update).

To discover updates faster, we have added auto-update functionality to ensure you have the latest version of SQL Operations Studio. A notification will pop up on the gear icon on the bottom left as shown in the image above. In addition, you can also check for updates by clicking Help on the toolbar.

Connection Dialog Database Drop-down

The Connection Dialog Database field is now a dynamically populated drop-down list that will contain a list of databases populated from the specified server.

New query tabs keeping active connection

A top voted feature by our users was for new query tabs to keep their active connection. In the February release, users can now click on a server name and press Ctrl + N, which will create a new query tab and retain the active connection instead of having to manually set the connection. This can be seen in the gif below.

Contact us

If you have any feature requests or issues, please submit to our GitHub issues page. For any questions, feel free to comment below or tweet us @SQLOpsStudio.

The post The February release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.

We are excited to announce the January release of SQL Operations Studio is now available.

Download SQL Operations Studio and review the release notes to get started. SQL Operations Studio is a data management tool that enables you to work with SQL Server, Azure SQL DB, and SQL DW from Windows, macOS, and Linux. To learn more, visit our Github.

SQL Operations Studio was announced for public preview on November 15, 2017 at Connect(), and this January release is the second major update since the announcement. If you missed the December release announcement, you can learn more on the SQL Server blog.

The January release includes several major repo updates and feature releases, including:

• Enable the HotExit feature to automatically reopen unsaved files.
• Add the ability to access saved connections from Connection Dialog.
• Set the SQL editor tab color to match the Server Group color.
• Fix the broken Run Current Query command.
• Fix the broken pinned Windows Start Menu icon.

For a complete list of updates, please refer to the release notes.

HotExit feature

A highly requested feature for SQL Operations Studio is to remember unsaved changes when the program is exited, similar to VSCode and other editors. We are excited to announce that HotExit has been enabled as demonstrated in the GIF above. SQLQuery2 represents an unsaved query, and the user can quit SQL Operations Studio and simply reload it again to retain the unsaved query.

This feature is not enabled by default. To enable HotExit by default, go to Settings with Ctrl + , and  copy “files.hotExit”: “onExit” into your settings.

Saved connections available in Connection Dialog

The Connection Dialog now contains a “Saved Connections” tab next to “Recent Connections”. This contains a list of saved server connections from the server’s “Object Explorer” viewlet, as well as the Server Group.

SQL editor tab color to match Server Group color

SQL query editor and dashboard windows will have the same color as the Server Group used to open the window. This feature is not enabled by default. To enable Tab Colors by default, go to Settings with Ctrl + , and  copy “sql.tabColorMode”: “fill” into your settings.

Contact us

If you have any feature requests or issues, please submit them to our Github issues page. For any questions, feel free to comment below or tweet us @sqlopsstudio.

The post The January release of SQL Operations Studio is now available appeared first on Microsoft SQL Server Blog.