The following query helps identify the columns associated with extended events and the format of the column i.e. int32.
As the data is typically extracted and used on SQL Server, I would have thought it would be more meaningful for Microsoft to actually use the SQL Server types i.e. bigint, nvarchar(MAX), instead we are supplied with a you guess field and it just adds another unnecessary frustration for the DBA / developer.
As part of a revamp of AKAWN Monitoring to include Azure SQL Database and Linux support the usual look at available monitoring options is being under taken.
Azure SQL Database is one of the trickier to monitor as it is pretty locked down and xml parsing for session events info can be hellish (one of the reasons the current AKAWN Monitoring is moving away from use of xml storage).
As locked down as it is, there are still ways to look into the inner workings. Just one example of the security things I’ve discovered is:
AKAWN Monitoring, our first product, has now been released to market as version 17.10.02.
It was a mammoth task and a great relief to finally have something to show for the effort.
So what does it take to produce a SQL Server monitoring product?
~ 2,700 man hours
~ 95,400 lines of written code
Learning a programming language and the quirks that it initials
A serious amount of designing, testing, further designing and then more testing in a continuous loop
~ 550 coffees :)
I’m sure there’ll be a couple of things that got by the copious amount of testing, but the product appears to be very stable and the documentation quite comprehensive.
It doesn’t end there, with SQL Server 2017 testing out the way, the focus now moves onto integrating Linux and cloud database support, query performance analysis, enhanced reporting and portal development.
So we hope you enjoy the product and help to make it the best one out there.