You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This topic helps to clarify the per-instance licensing of IDERA SQL Secure when dealing with Azure SQL Database instances.

In a nutshell, you add Azure SQL Database to monitor in SQL Secure using the instance name, just as you do with on-premises and IaaS instances, so IDERA licensing works the same way.

Longer answer: In Azure SQL Database there is still the logical construct of a "SQL Server," although a PaaS implementation of it. When you set up an Azure SQL Database in the Azure Portal you do so by creating a SQL Server (which is not to be confused with a SQL Server running on a VM) and then you create databases. Here are some illustrative screenshots:

In these examples, the SQL Server "lenticular"  - which is located at lenticular.database.windows.net - is the host for my Azure SQL Databases. In SQL Secure, I register the "lenticular.database.windows.net" name and have access to all of the SQL Database databases in that instance - two, in this case.


IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal

  • No labels