![]() ![]() ![]() In fact, as you read this, we’ll have already started. And now the time has come to step up, dig in, and do my due diligence.Īs Randy mentioned in his latest blog post, we’re going to take the leap and use Azure Data Studio exclusively (or as exclusively as possible) for the next 30 days. Part of the research included talking to one of the PMs on the tooling team and getting some insight. Thus, my quest of recent has been to do a deep analysis of both tools and determine if I am underselling ADS and, can I be more efficient as a DBA using it? Or, are these for two completely different audiences? So why do I have it installed? I don’t know…probably because somewhere deep in my psyche I want to believe and just haven’t made the leap. The truth is I’ve had ADS installed for a LONG time, and I keep it up to date (just like SSMS, it has monthly updates). Is that still the case? Can I manage availability groups (AGs) or dig into the Query Store? Can I even mouse click on the databases node and select “new database”? I’m a database professional, and the last time I used ADS, it was missing a lot of the UI features and functionality for managing database environments. Here’s the thing: If Microsoft is going to force ADS on me, it needs to provide a decent level of DBA coverage in terms of features and functionality, comparable to SSMS. But, I keep getting caught up on the “for database professionals” part. I could not agree more with the cross-platform support, as this is definitely needed. The answer was Azure Data Studio (initially released in 2018 and known as SQL Operations Studio), a cross-platform tool that, as the Microsoft documentation states, is “for data professionals using on-premises and cloud platforms” that works on Windows, macOS, and Linux. SSMS is Windows only, and with SQL Server now supporting Linux, it was time for some changes. However, the winds of change also dictated that we needed something newer and more effective to support both on-premises and the cloud, and across platforms. The UI hasn’t changed but at least it’s getting some regular love. That changed not long ago when Microsoft decided to decouple the SSMS install from the SQL Server install, allowing regular updates for and bug fixes for SSMS. And even then, it was still looking its age. As such, you had to wait until the next release of SQL Server to get any updates to SSMS. Meaning, Microsoft updated it only when they updated SQL Server. It isn’t a secret that, up until a few years ago, SSMS was getting long in the tooth. I realized I didn’t know enough about ADS to know if it is a tool I can use every day in my role as a DBA. So, after I stewed a bit, I thought I needed to “back the bus up” and think about this a little more - approach ADS from a different angle. Second, the last time I used ADS, which was, admittedly, quite some time ago, it was super light on the functionality I need as a DBA. First, why is Microsoft forcing ADS on me? That just does not seem right. This bothered me for a couple of reasons. Meaning, if I wanted the latest SSMS, I’ll also get ADS if I want it or not. What annoyed me is that it didn’t give me the option to install it Microsoft forced it on me. ADS has been included with the SSMS install since version 18.7. I was a bit surprised that, as part of the SSMS update, I ended up with Azure Data Studio (ADS) as well.Īs of this writing, the latest version of SSMS is 18.8. I downloaded the update and started the install. It had been some time since I had opened it (typically I use SSMS installed on the client’s machine), so I got the popup message that there was an update. The other day I opened SQL Server Management Studio (SSMS) on my laptop.
0 Comments
Leave a Reply. |