azure-table-storage

The following code returns blob file size of 0: public long GetFileSize(string fileUrl) { var blob = GetBlobContainer().GetBlobReference(fileUrl); return blob == null ? 0 : blob.Properties.Length; } , its almost as it does not find the blob. But of I delete the blob I see that it gets deleted. This works when deleting: void DeleteFileFromBlob(string fileUrl, bool deleteSnapshots) { var blob = GetBlobContainer().GetBlobReference(fileUrl); if (deleteSnapshots) { var options = new BlobRequestOptions { DeleteSnapshotsOption = DeleteSnapshotsOption.IncludeSnapshots }; blob.DeleteIfExists(options);

We have a bot deployed on Azure but we want to give it to a client so he can deploy it run it using his own resources. We need to give them a Powershell script that magically create and deploy all the resources needed for the bot to work. My bot architecture consists on the following parts: Bot's Logic (ASP.NET Web API Project deployed over an Azure App Service ) LUIS Model (published over a Cognitive Services Account ) QnA Service Knowledge Base done with QnA Maker ( published directly from the QnaMaker Portal (have no idea where it's deployed ) Azure Table Storage My Questions are: 1) How to

I am creating a basic (my first) Azure Mobile Service with Table Storage to control a simple Events app. My DataObjects consists of 2 object types: Coordinator and Event , I want Coordinators to be a separate table to store specific info that I don't want it denormalized inside the Events, but Events also has a inner object Location to store details for the event's location, but that I want to store denormalized as I don't want to maintain this details separately from the Event. Here the objects I have so far: DataObjests: public class Coordinator : EntityData { public string Name { get; set;

Is it possible to create a directory like structure in Azure Tables? I need to store some metadata in a tree like structure. For example if I have 10 items and each item contains some metadata columns (there are some common columns for all of them [id, name, date created, author ... ], but might be also some columns that one item might have but another one no) Can these items be stored in a structural way? Item1 |_____ Item2 |_____ Item3 |_____ ItemX You can't nest the way you describe, but using Azure Tables, you don't necessarily need to. In the example above, I would set Item1 = Partition

Take a 100gb database for this example: Azure Storage cost: £6.05/m MongoLab on AWS with 1 node cost: £153.18 /m Am I missing something? Calculated something incorrectly? Can someone clear things up for me here? I would much rather use MongoLab as I really like node/mongoDB. But it seems a much more cost effective solution to go with the Table Storage. I know the differences between Key/Value and Document store and I do prefer the latter. You need to consider that Azure Table Storage (ATS) is storage-as-a-service. You don't need to set up any servers to manage the storage and related CRUD

I am adding a new column to my azure table. For ex., the table is called 'User' and the new column is called 'ComputationDate'. The 'User' table already exists with rows that do not have this new column 'ComputationDate'. I have a query over it as follows, var usersDue = from user in Table.Query where user.ComputationDate != <somedate> select user; I want this query to return all user rows that do not have ComputationDate set to 'somedate' and also user rows that do not have this new 'ComputationDate' column defined. But the query doesn't return the latter set of users. It only returns rows

Background I am receiving CSV data files from clients that contain a large amount of data that I don't need and a small amount of data that I do. In the future I may need to access that data and although I'm archiving the original data files I was hoping for something a bit easier to query. I was hoping for a solution that didn't mean the data files stayed in the same format - i.e. the client may add/remove columns and I don't want my implementation to bail on missing data or fail to archive additional data. As I'm building the application in Azure, Azure table storage looked correct to me - I