Identify columns available for extended events

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.

How secure is Azure SQL Database?

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:

The above method will show buffer activity for all sessions, which is a big no no and something Microsoft will likely need to look into locking down.
 
What does it show? Well basically everything i.e. it shows the checks performed, shows when and where backups are going along with the syntax used:
 
(@DbName nvarchar(36),@BackupStats int,@BufferCount int,@TransferSize int)BACKUP LOG @DbName TO URL = N'https://xxxx.blob.core.windows.net/server-akawnxxxx/backup/xxxx/Log/2017-11-26T12-02-06/2017-11-30T23-13-25_2017-11-26T12-02-06.log' WITH COMPRESSION, INIT, FORMAT, CHECKSUM, STATS = @BackupStats, BUFFERCOUNT = @BufferCount, MAXTRANSFERSIZE = @TransferSize
 
If you collected info for long periods, who knows what could be revealed.

 
The above was collected from a standard azure database and not master, although you could just as well use it.
 
I haven’t seen anyone else mention this, so you’re reading about this first here.

What’s the local time?

SQL Server has a handy view called sys.time_zone_info, but as shown below it’s lacking the local time.


 
The following is one way to workout the local time:


Or just a specific zone:


Hopefully at some stage Microsoft will look to include the local info by default so this kind of work around is not required, especially as Azure is heavily invested in UTC.

Choosing a SQL Server edition during setup on Linux

You may be wondering how you specify the edition of SQL Server when installing on Linux.
 
As shown below; when you get to the step sudo /opt/mssql/bin/mssql-conf setup the following edition options are presented to you.
 

Here option 2 (Developer) was selected and this presented a further set of 3 questions before the setup successfully completes:

      1) Accept the license terms
      2) Choose the language
      3) Confirm the sa password


AKAWN Monitoring v17.11.05 released

AKAWN Monitoring version 17.11.05 has now been released and is ready for download.
 
This release introduces index/heap info and trending along with easy visual references for potential issues i.e. disabled indexes, hypothetical Indexes etc
 

If you have any feedback, please don’t hesitate to contact us by either logging in and raising a support ticket or sending us an email at support@akawn.com.
 
Cheers the A team

AKAWN Monitoring v17.10.24 released

AKAWN Monitoring version 17.10.24 has now been released and is ready for download.
 
With the new powerful Query Activity feature, you can schedule when to collect query activity or stick with the default every 15 minutes.
 
With well over 100 query metrics reviewed for collection, troubleshooting query performance issues should become a lot easier.
 
As always, if you have any feedback, please don’t hesitate to contact us by either logging in and raising a support ticket or sending us an email at support@akawn.com.
 
Cheers the A team

AKAWN Monitoring v17.10.10 released

AKAWN Monitoring version 17.10.10 has now been released and is ready for download.
 
It includes the following updates:

  • AKAWN Studio – Fix: Show Columns in Database Configuration Settings
  • AKAWN Studio – Fix: Maintenance model parameter check correction
  • AKAWN Studio – Fix: Integrity Checks increase initial instance connection timeout
  • AKAWN Studio – Fix: Instance and Server alerts hide checkbox
  • AKAWN Studio – Enhance: Increase wait cursor visibility during maintenance tasks startup and refreshing
  • AKAWN Server – Fix: Exclude snapshot databases from the “Backups full missing” and “Backups log missing” checks

If you have any feedback, please don’t hesitate to contact us by either logging in and raising a support ticket or sending us an email at support@akawn.com.
 
Cheers the A team

AKAWN Monitoring RTMs

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.
 
Cheers the AKAWN team