windows-azure-storage | Microsoft Azure Storage service to host your website | Azure library

I am creating an avro schema for a JSON payload that appear to have an array of multiple objects. I'm not sure exactly how to represent this in the schema. The key in question is content:

I'm very new to Azure and have been tasked with automating the process of taking an existing version of our database, converting it to the newer version and then uploading that to Azure.

The conversion is done, that parts easy, what I'm struggling with is getting a .bacpac file from SSMS using PowerShell. I know I can use the Export Data Tier Application function in SSMS to do this but I need it to be automated. From there I can use something like the following to actually upload the database:

https://blogs.msdn.microsoft.com/brunoterkaly/2013/09/26/how-to-export-an-on-premises-sql-server-database-to-windows-azure-storage/

I have looked around and cannot find a solution to this, or even know where to start.

I'm trying to move the azure storage log file into azure storage tables so I can more easily work with them, but I noticed this

"duplicate log records may exist in logs generated for the same hour and can be detected by checking for duplicate RequestId and Operation number."

source:https://blogs.msdn.microsoft.com/windowsazurestorage/2011/08/02/windows-azure-storage-logging-using-logs-to-track-storage-requests/

(I know it's an old article, but it's all I can find)

With this in mind, I thought it would be sensible to use a concatenation of the requestID with the operationID as my row key.

I wanted to check if anyone is aware just how unique the requestID is (Apparently some requests might have more that 1 operation such as "copy", but most will have just 1).

If I'm using it as a row key, I can't afford for it to appear twice in the same partition (Partitioning by userID, but lets suppose each partition can contain millions of records).

Thanks

We are in the process of creating a piece of software to backup a storage account (blobs & tables, no queues) and while researching how to do this we came across the possibility storage logging. We would like to use this feature to do smart incremental backups after an initial full backup. However in the introductory post for this feature here the following caveat is mentioned:

During normal operation all requests are logged; but it is important to note that logging is provided on a best effort basis. This means we do not guarantee that every message will be logged due to the fact that the log data is buffered in memory at the storage front-ends before being written out, and if a role is restarted then its buffer of logs would be lost.

As this is a backup solution this behavior makes the features unusable, we can't miss a file. However I wonder if this has changed in the meantime as Microsoft has built a number of features on top of it like blob function triggers and very recently their new Azure Event Grid.

My question is whether this behavior has changed in the meantime or are the logs still on a best effort basis and should we stick to our 'scanning' strategy?