SQL Monitor 10.1 now gives you a comprehensive overview of your SQL Server licensing, so you know which licenses are in use, and which versions are on which servers. This simplifies license auditing and lets you unearth misconfigurations that could potentially cost you money. The new version also integrates with Microsoft Teams and Splunk, and supports complex Active Directory environments.
2020-07-02
Phil Factor creates a simple custom metric to track the number of sessions that have recently done a read or write on a database. Having established a baseline for the metric, you'll be able to spot, and investigate the cause of, any wild deviations from normal behavior.
2019-04-25
Last year we ran the industry’s first ever state of SQL Server monitoring survey, the results not only gave great insight for the community but helped us shape our product development to ensure we were meeting the needs that you were asking for. So what has changed in a year? Tell us for your chance to win a $250 Amazon voucher.
2019-04-03 (first published: 2019-03-21)
2,280 reads
In this blog, we review the key insights from last year’s State of SQL Server Monitoring report. One year on, how has this changed? Read the blog to find out how you can help us define the state of 2019 plus a chance to win a $250 Amazon voucher.
2019-04-02 (first published: 2019-03-18)
1,864 reads
Data analysis is all about wrangling massive datasets. To do that efficiently, you need...
By Rob Sewell
Make it easier for your audience to engage with you by connecting your site...
By Rayis Imayev
"Stories are where memories go when they are forgotten" - Doctor Who.(2024-Sep-13) As September quickly...
Comments posted to this topic are about the item GIT Configuration and Automated Release...
I have a Colum that outputs this data, depending on the Card Type: 0991719957291436|02|22|VISA|Visa|...
Comments posted to this topic are about the item Trigger Order III
I have created these triggers in SQL Server 2022:
CREATE TRIGGER triggertest_tri_1 ON dbo.triggertest FOR INSERT AS PRINT 'one' GO CREATE TRIGGER triggertest_tri_2 ON dbo.triggertest FOR INSERT AS PRINT 'two' GOI want to be sure that the trigger with "1" runs first. I decide to run this:
EXEC sp_settriggerorder@triggername = 'triggertest_tri_1', @order = 'first'What happens? See possible answers