Skip to main content

SQL Azure - Improve restoring time of BACPAC during load tests

SQL Azure is a great service when you need a location to store a relational database and you don't want to manage the infrastructure that is behind it. In only a few minutes, you can get a powerful database ready for your needs.

In almost all projects life cycles, there is a moment in time when need to run one or more Load Tests. For each scenario, you may need a different database setup.
In the above example, we have 3 different scenarios that we want to test. This means that, we need to load 3 different bacpac files. If the database is relatively small (10MB) than we will not have any kind of problems.
But with a large database, the restoring process can take some time. Behind the scene, a database restoring process is complex and CPU intensive, because of this it will require time and CPU.
This will not be a problem for a database of type P1 or P2, where the restoring process is fast. But, for a S0 or S1, we may need to wait for even a few hours, until our backup is restored and our database is ready to run another load test scenario.

What we could do in this case? What we can do to reduce the waiting time between Load Tests?
Better databases
One possible solution would be to upgrade our database to a better one. Unfortunately this is not a solution. When you run a load test you want to run with the same configuration like in production. Running with a better database may affect your load tests results.

Different databases
Another solution is to prepare multiple databases, with different configuration. In this way you can have for each scenario a different database instance. From your application you could specify what database you want to use.
This could work for small/medium solutions. But this could increase the load test setup if your system use 15 different databases for example. Also, the costs of running the load tests may be impacted.

Better databases only when we restore a bacpac
Using this approach, we would run the load test with the database type that we want. Only during the load test setup, we would upgrade our database instance to a better type. In this way we can minimize the time that is needed to restore a specific bacpac and we would also reduce the costs of the load tests.

 
It is important to know that changing the type of a database takes only a few minutes. In this way we can easily play with different types.

In conclusion we could say that the best approach in this situation is to use the same database, but to change the type of the database when a database restore is done. This would allow us to keep the time and the costs to minimal and well-balanced.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…