Skip to main content

Data Model for Reporting over Windows Azure Tables (part 2)

Part 1
In the last post we talked a little about how we can calculate TOP 5 visited URLs per day for each user and TOP 5 visited URL anytime. For these cases I propose some ways on how we can store information on Windows Azure Table in a way that we can generate these reports.
In today post we will see how we can resolve the concurrence problem. We can have 10, 20 or 100 commands that want to execute over the same entity from Windows Azure Table. Because of this we need to guaranty that the writer has the last version of the entity before update it. If we will not be able to guaranty this… than our reporting solution will be compromised.
Windows Azure Table comes with a simple solution. Each entity that is stored on tables contains a unique key named ETag. ETag is changed every time when the entity is updated or changed. Based on this value we can know if we have the last version of an entity or the entity was changed from the moment when we receive it. ETag is the secret that give us support for concurrency access to Windows Azure Storage (Tables and Blobs).
Each entity that is retrieved from Windows Azure Tables has the ETag set. When someone will update any field from the given entity, the ETag value will be changed. In the moment when another user tries to make an update with an invalid ETag, the merge option feature will be used.
The data context contains a merge option filed that can be set manually. Based on this value, we can provide a custom behavior when a conflict appears. The values that are supported for MergeOption enum are:
  1. AppendOnly (default value)
  2. OverwriteChanges
  3. PreserveChanges
  4. NoTracking
For a description of this values please take a look here.
We saw that Windows Azure tables already have support for object “versioning” and automatic detecting and resolve merge conflict.
This can be used with success in our problem, when  in the case when the entity was update by another client we will need to retrieve the last version of the entity and update it.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…