Based on this combination of features, one can draw the conclusion that Microsoft is now shifting toward closing the gap between Azure Data Studio and SQL Server Management Studio, making it a viable alternative for developers and DBAs alike. This page lists all features supported for the Microsoft SQL Server database. Buy Pro Version. HiDPi images on Mac Retina displays. Task Management and Memory Monitoring Feature. DbVisualizer Pro. DbVisualizer Free. Central Task Manager.

I love free tools. I also love analyzing SQL Server’s wait statistics. But I’m not a fan of Activity Monitor, a free tool in SQL Server Management studio, which helps you look at wait stats.

Activity Monitor just doesn’t give you the whole truth. I against a test SQL Server 2014 instance. My workload runs a query that’s very intensive against tempdb, and it’s really beating the SQL Server up by querying it continuously on seven threads. Let’s look at our wait statistics.

Here’s what Activity Monitor shows in SQL Server 2014. Here I get specifics on exactly what type of wait is is and the related query. Let’s compare.

Activity monitor groups wait types. It took a whole lot of waits and rolled them up into ‘Buffer Latch’. This isn’t necessarily a bad thing, but I’ve never heard of documentation that explains what’s rolled up into which groups.

By comparison, sp_BlitzFirst showed me the specific wait types PAGELATCH_UP, PAGELATCH_SH, and PAGELATCH_EX, with the amounts for each one. Sp_WhoIsActive even showed me the type of page that is having the bottleneck (GAM) and the database and data file (tempdb’s data file 1). Activity monitor leaves out wait types. sp_BlitzFirst showed that in aggregate, my #1 wait was CXPACKET over the sample.

Word for mac making duplicate labels. That tells me that a lot of my queries are going parallel. That’s not necessarily a bad thing, but it’s important for me to know that about my workload at the time.

It helps me know that I want to learn more, and make sure that the right queries are going parallel. (In this case, the query that’s going parallel is pretty cheap, and is just as fast single threaded. My throughput goes up dramatically if I adjust the Cost Threshold setting up a bit.) Friends don’t let friends use Activity Monitor. It may be convenient, but it doesn’t tell you the truth.

Do yourself a favor and use a free tool that gives you wait statistics straight up. That’s the NEW name SW gave it. When you download, it’s Ignite_f_8_3_407_setup.exe, as of last week, that is. If you click the download button, you register (it’s easy to unsubscribe) and you’ll see a product image that shows, at top left, “Ignite”. I have it watching 5 servers on 3 different domains from one webpage. Must admit that some of the language in the setup pages is “different”, for an accidental DBA like me, but it’s worth wading through.

SQL Login for the ignite_repository (SQL Database on a dev server), I think I took the defaults, but used sa just for the install, and you assign the strong password. So, I would like to speak in Activity Monitor’s defence. I think that as long as you are aware o Its limitations, it is a good basic tool to give you that mile-high overview of what’s going on in a particular SQL Server instance. I agree that it should NOT be used as the definitive too for rooting out performance issues and I ageee there are much better tools out there If you were ever a Unix sys admin, I think you relate to the anology of the vi editor.

The best thing you can say about it is “It’s always there”. Except vi/vim editors aren’t just basic tools when it comes to Unix tools that are “always there”. After all those years they are superior compared to a lot of younger editing/programming tools. Do you need antivirus for mac book.