Comments
5 comments
-
Hi @postledm
Thank you for reaching out.
I'm afraid that from SQL Monitor 9 and onwards we specifically only connect to the Primary.
This has been raised as a feature request though on our uservoice forum so you can add your vote to this if you'd like to see this feature in the future:
https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/41525422-monitor-azure-sql-read-scale-out-database -
Adding the
ApplicationIntent=ReadOnly
parameter to your connection string in SSMS ensures that the connection is directed to a read-only replica of the database. This can help offload read-heavy queries to secondary replicas, improving performance and reducing the load on the primary database instance. -
-
You can achieve this by using an OUTER JOIN with a table or dataset that contains all possible layers and titles. This ensures that even if a filtered business unit has missing layers or titles, they still appear as blank rows in the view. You can also use COALESCE() to fill missing values with placeholders. Additionally, GROUP BY with conditional aggregation can help maintain structure while filtering. If you're using SQL Server, consider using a CROSS JOIN with a predefined list of layers and titles to ensure consistency across different filters.
-
You can accomplish this by performing an OUTER JOIN with a table or dataset that includes all possible layers and titles. This guarantees that even if certain layers or titles are missing for a filtered business unit, they will still appear as empty rows in the result. Using COALESCE() allows you to replace missing values with placeholders. Additionally, applying GROUP BY with conditional aggregation helps maintain structure while filtering. If you're working with SQL Server, a CROSS JOIN with a predefined list of layers and titles can ensure consistency across different filters.
Add comment
Please sign in to leave a comment.
ApplicationIntent=ReadOnly