Those who closely follow this blog and myself will know that SQLWATCH and thus this blog were an offshoot of my original blog, firstly at https://marcingminski.com and then https://marcin.gminski.net. It all started with this post https://marcin.gminski.net/blog/sql-server-performance-dashboard-using-powerbi/ and this is how SQLWATCH was born and how I ended up with essentiall two blogs in the same
If you can’t explain it simply, you don’t understand it well enough.Albert Einstein
Blogging helps me understand problems better and pass this knowledge onto you. I blog and we both learn. I hope you find it useful and please comment and share your views!
One of the biggest challenges I face when building SQLWATCH is testing. Up until recently SQLWATCH distributed-only solution. It means that it had to be installed on each monitored server and only worked in a local scope. This made the development and testing easy as I only had to make sure that it runs on
Apologies if you have received an email with random test content. I wanted to try a new template for the website and blog and somehow it decided that it will be a good idea to auto-post and thus trigger an email with some demo-content. #NeverTestInProduction
I get a lot of emails with concerns that some of you have very strict security and locked-down environments which prevent you from installing SQLWATCH. At the same time, some of you would have preferred the central repository to connect directly to the remote instance and pull data out of it. Let’s discuss this problem.
The identity value in relational databases is a field that increases automatically. It is often used to create surrogate primary keys. Surrogate keys Surrogate keys are meaningless and are only used to uniquely identify the row, not the data itself. For example, assume the following table: As we can see, the identity values are 1,
I recently came across a tweet by Brent Ozar who touched on a very important aspect of performance monitoring. A subject that is not always well understood and can lead to misleading results. The impact of aggregation on granularity and thus observability. Brent’s tweet inspired me to try and explain the matter in more than
The observer effect is a term used in physics and it means that observing a phenomenon changes that phenomenon. Therefore, an object that is being observed, is looking different to the same, not observed object. How is this possible? In physics, this is to do with photons and electrons. An electron is only detected by
Hey SQLWatchers, First of all, thank you for the growing community and for using SQLWATCH. SQLWATCH has reached over 10000 downloads. This does not include source code downloads and offline installations. I am myself aware of many places that download the release or source code once and deploy to their servers. The total instances monitored
In the previous post, I have explained how to configure SQLWATCH To send simple, plain text notifications to Microsoft Teams. Today, we are going to look at how to send formatted cards: Action templates Formatted cards require slightly more complex JSON structure and for that reason, we are going to create a new message template.
Some time ago we discussed how to send notifications to Microsoft Teams: In this post, we are going to look at doing the same with Slack. The only difference between these two platforms is in the payload they expect. Beyond configuration of the correct action, the action association process is exactly the same in both