Hi Praveen,

In BODS you can create a file location which uses the azure cloud storage protocol.

You need

Account Name: Can be found in Azure

Account Shared Key: Can be found in Azure

Local Directory: Some folder on you Data Services Server or on a network drive. BODS will transfer the file to the local directory and upload it afterwards to the blob storage.

Container: Container in your blob storage. This can be created in Azure or BODS will it create during the batch job.

This file location can be associated to a flat file format

The flat file format can be used in every batch job.

First BODS copies the file to the local directory. When this is done, it will be uploaded. So BODS does it sequentially.

You should consider a script which deletes the file after a succesfull upload. Otherwise you local storage will be full sooner or later.

Since BODS is not able to write into Append Blobs, you are not able to update the data in the blob. Except you overwrite the file when you use the same name. If you do a full load every time, it would be an option.

Otherwise I recommend using a variable for the filename with a timestamp. (you can see it in the screenshot above).

This is how I do it:

$filename = to_char(sysdate( ),'YY')||'_'||to_char( sysdate( ),'MM')||'_'||to_char( sysdate( ),'DD')||'_'||to_char( systime( ),'hh24miss')||'_<TABLENAME>.dat';

Hope I could help you!

Best regards

Scott