However, you will need to take a few steps to see these improvements in action.įirst, you’ll need to make sure you have version 1.35.0 of Azure Data Studio. These are officially still in preview, but they are already available. I am writing this post because Microsoft has made huge improvements to execution plan support in ADS. Futureīut I am not writing this post to moan about past issues. That is, of course, totally useless for a serious developer trying to troubleshoot the performance of a stored procedure. There rest of the execution plans were only “shown” as XML output. When running a batch with multiple T-SQL statements, the tool would only render the execution plan for the first query. If a property was not included in the UI design of ADS, there was no way to get its value (short of accessing and parsing the XML representation of the execution plan).Īnd while we are at it, let’s not forget the bugs. In SSMS, one can debate the choices Microsoft made towards which properties are exposed in the popup window we see when we hover an operator, but we can at least always open the Properties window to access the full properties list. We need to dive in and check the properties for a better understanding. Looking at the icons and the arrows is just the beginning. Properties are, of course, the most important part of execution plans. This means far more scrolling is needed when working with larger execution plans, and it’s much more challenging to see the overall picture. A more objective issue I have had since first seeing the ADS execution plan interface is that many operators, including a few very common one, have either a generic icon or no icon at all!Īnother issue I had with the ADS display of execution plans is that the icons used up much more screen space. Beauty is, of course, in the eye of the beholder but I have yet to meet someone who actually prefers the design of the ADS icons over the SSMS icons. That adds needless complexity to the jobs of developers, as well as to trainers. The icons used to represent operators were all different from the icons that people were used to from working with SSMS. But I would severely hesitate to call it serious support. There has, indeed, always been support for viewing execution plans in ADS. If ADS wants to be a serious tool for the serious developer, then it must have serious support for working with execution plans. Both roles should be able to access the execution plan of a query. Query tuning is, in my opinion, part of the job of both DBAs and developers. But a developer will rejoice at having a tool that doesn’t require Windows but also runs natively on Linux or macOS, and that connects to almost every data provider instead of just SQL Server and Azure SQL databases. A DBA will notice that lots of actions typically associated with their job of database administration have no or very limited support in the GUI, though they can of course still be done with T-SQL statements in a query window. This tool seems to be mostly targeted towards developers. The alternative is Azure Data Studio (ADS). SQL Server Management Studio (SSMS) is for many people still the default choice it used to be included with a SQL Server installation, it is the most familiar tool for most SQL Server professionals, it gives easy access to (almost) all SQL Server features, and it’s simply the interface we have been used to for as long as we’ve been working with SQL Server. Microsoft has two main tools for querying and managing SQL Server databases in a graphical UI.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |