Table of Contents
In this blog post, we’ll look at getting version information from your Azure Synapse Analytics SQL pool using T-SQL. This information could be different within databases in the same region.
In my previous post, we defined maintenance windows for an Azure Synapse Analytics SQL Pool. It’s important to be aware of any new changes that become available and the status of your current service.
To find out information about the version, engine edition, and product version, execute the following command:
SELECT [Version] = @@Version, [Engine] = SERVERPROPERTY('EngineEdition'), [Product] = SERVERPROPERTY('ProductVersion')
The expected result will look like the row below.
Why is this relevant? Because you could have different versions across regions and within the same region!
Most times, the new product version will be applied after pausing and starting the service.
Let’s take a look at an Azure Synapse Analytics product version in the same region.
And finally, let’s check out an Azure Synapse Analytics product version in another region. You’ll find that the product version is different.
This is something that you want to take into account when working with Azure Synapse Analytics.
How can I keep up to date with new features?
Integrate the RSS feed from the following Microsoft Azure site with any messaging/workflow platform such as Teams or Slack, or use Power Automate.
Review the Microsoft release notes (I’d like to see the URL matching the engine version.)
Check Github repository commits.
We’ve seen how to get the version of Azure Synapse Analytics and check the latest update, identifying the product and engine version.
Since I work for a technology edge consultant company, understanding how Azure Synapse Analytics features are different between databases and being up to date with any possible outages is important for me and our clients.
In upcoming blog posts, I’ll cover some other features within the data analytics space and Azure services.