You can use read only replicas but they are not frozen so they can receive some new data.
Maybe you can fix the issue with some kind of filter based on insert/update datetime.
Azure SQL Database doesn't support Database Snapshots, so there's no other option besides:
Running the reporting queries in a SNAPSHOT transaction.
Creating a consistent copy of the database with COPY or point-in-time restore.
First you will need create a contained database user inside Azure SQL Database, run below:
create user [firstname.lastname@example.org] from external provider
Alternatively assign AD user/group of admin(s) on Azure SQL Server level
Then use the "Active Directory - Universal with MFA support" authentication type in SSMS
From the "SQL Server ...
You should directly extract the values from the json array using the WITH clause, like this:
FROM json_test src
CROSS APPLY OPENJSON(src.the_json , 'lax $')
[name] sysname '$.name'
, [object_id] int '$.object_id'
The dbcreator role doesn't exist in an Azure SQL Database because there are no server level roles in the Azure SQL Database product.
You can find which types of Microsoft database products do support it on the Server-Level Roles documentation. It appears to just be SQL Server and Parallel Data Warehouse.
For further information on provisioning administrative ...
As Microsoft Docs, "/p: DatabaseMaximumSize=(INT32)" Defines the maximum size in GB of an Azure SQL Database. So, I realized database size is know as in GB. So I used
for database size 60GB:
"import parameter /p:DatabaseEdition=GeneralPurpose /p:DatabaseServiceObjective=GP_Gen5_2/ p: DatabaseMaximumSize=60"
Just found in the documentation:
Database copy is not supported when the source and/or destination servers have a private endpoint configured and public network access is disabled. If private endpoint is configured but public network access is allowed, initiating database copy when connected to the destination server from a public IP address will succeed. ...
You have a couple of choices here:
I know this does not let you save it in a table, but you have access to 30 days of CPU usage at any point without you doing anything. This is via matrics.
To collect the data from the two System dynamic management views I mentioned below, you can set up a collection at a set interval (similar to SQL Agent job) by using one ...