Connect a Microsoft Azure SQL Database (managed SQL Server) to SMAQ.
In the Azure Portal:
SQL databases → click your database.
From Overview, copy the Server name (e.g. acme-prod.database.windows.net).
Note the Database name.
Default port is 1433.
[Screenshot needed] Azure SQL Database Overview pane with Server name and Database name highlighted.
SQL Server → Networking (the server resource, not the database).
Toggle Public access to Selected networks (if not already).
Firewall rules → Add a rule for each SMAQ outbound IP. Get the IPs from [email protected].
Save.
[Screenshot needed] Firewall rules pane with SMAQ IPs listed.
Connect to your DB as admin (via Azure Data Studio, SSMS, or sqlcmd):
SMAQ project → Data Source → Add data source.
Pick Microsoft Azure SQL.
Fill in:
Host: the server name (acme-prod.database.windows.net)
Port: 1433
Database, Username (smaq_readonly), Password
SSL mode: Require (Azure SQL always uses encrypted connections)
Test connection → Connect.
"Cannot open server requested by the login" — Azure firewall isn't allowing SMAQ. Double-check the IP rules and that you edited the rules on the server, not the database.
"Login failed for user" — the user was created at the database level but the login wasn't created at the server level. Re-run CREATE LOGIN ....
Slow queries — Azure SQL has a service tier that limits DTU/vCore. Cheap tiers throttle aggressively under analytical workloads.
SMAQ doesn't currently support Azure AD-based authentication for Azure SQL. Use SQL authentication (username/password) instead. Talk to [email protected] if AAD auth is a hard requirement.
Last updated
CREATE LOGIN smaq_readonly WITH PASSWORD = 'long-random-string';
USE your_db;
CREATE USER smaq_readonly FOR LOGIN smaq_readonly;
EXEC sp_addrolemember 'db_datareader', 'smaq_readonly';