2 votesDimitri Furman shared this idea ·
Upvotes: 8<=-=Mar 18 2017 4:59AM=-=>
So sadly given the lack of a response to this my scenario cannot wait and we’ve abandoned backup to Azure URL since it doesn’t support the functionality required and there’s no information on if it ever will.
MAXTRANSFERSIZE is supported for backup to block blobs, for SQL Server 2016 and later.
In terms of hardware resources, all replicas are identical. Currently, you can see resource utilization and other performance metrics (i.e. waits) on a Read Scale-out secondary if you connect to it in SSMS or another client specifying ApplicationIntent=ReadOnly, and then query corresponding DMVs, such as sys.dm_db_resource_stats and sys.dm_db_wait_stats.
4 votesneed-feedback · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Can you please provide more feedback, as Dimitri asked in a comment below:
Thanks for bringing this up. Could you please elaborate on what you are trying to achieve in more detail? Would the information provided by sys.server_principals and sys.server_permissions DMVs be sufficient, and if not, why?
SQL Trace and SQL Profiler are deprecated. Similar functionality is provided by Extended Events. Please see https://docs.microsoft.com/en-us/azure/sql-database/sql-database-xevent-db-diff-from-svr, and http://www.mssqlgirl.com/using-extended-events-on-azure-sql-database.html.