azure-sql-database

Ok not sure what to enter in the subject line so apologies if it stands unclear. I created a simple web app using MS Access 2013. It simply had one table with sample data in it. The I launched it to my share point. Before we go ahead, I would like to tell you that I am using Office 365 enterprise version where we need to admin everything like Lync/SharePoint/Exchange etc. So as per Microsoft blogs and articles and discussions all over, and even the following screenshot suggests that the data stored in the Office 365 is stored in a SQL Azure database for office 2013 web app. So as the next step

I've been hunting for this error that occurs intermittently on an AJAX call to an Azure ASP.NET Website, and today I've finally caught it in our logs. I was suspecting a lock was blocking the operation, but it looks like it failed trying to connect to the Azure SQL database. Here is the exception message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. This failure occurred while attempting to connect to the routing destination. The duration spent while attempting to connect to the original server was - [Pre-Login]

Now that Microsoft made the new SQL Azure service tiers available (Basic, Standard, Premium) we are trying to figure out how they map to the existing ones (Web and Business). Essentially, there are six performance levels in the new tier breakdown: Basic, S1, S2, P1, P2 and P3 (details here: http://msdn.microsoft.com/library/dn741336.aspx ) Does anyone know how the old database tiers map to those six levels? For instance, is Business equivalent of an S1? S2? We need to be able to answer this question in order to figure out what service tiers/levels to migrate our existing databases to. We just

I am at the planning stage of a web application that will be hosted in Azure with ASP.NET for the web site and Silverlight within the site for a rich user experience. Should I use Azure Tables or SQL Azure for storing my application data? Azure Table Storage appears to be less expensive than SQL Azure. It is also more highly scalable than SQL Azure. SQL Azure is easier to work with if you've been doing a lot of relational database work. If you were porting an application that was already using a SQL database, then moving it to SQL Azure would be the obvious choice, but that's the only

Full exception: System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: Session Provider, error: 19 - Physical connection is not usable) Why isn't this handled by the SqlAzureExecutionStrategy ? Especially because this happens during VIP swaps. Is it a good idea to write an own DbExecutionStrategy that handles this one, or am I missing something? From the profiler trace we

I have an ASP.NET MVC 4 project which is to be deployed to Azure for production, in production I use a SQL Azure database. My problem is that I want to connect to the SQL Azure database only in the production deployment, and not when developing, and that the SQL Azure connection string should be encrypted. Now, I can solve the first requirement through a Web.config transform, so that the database connection string gets substituted upon deployment to Azure. However, I don't see how to combine this with connection string encryption? How can one both encrypt the SQL Azure connection string and

My organization needs to have a shared database, shared schema multitenant database. We will be querying based on TenantId. We will have very few tenants (less than 10) and all will share the same database schema with no support for tenant-specific changes or functionality. Tenant metadata will be stored in memory, not in the DB (static members). This means all entities will now need a TenantId, and DbContext needs to know to filter on this by default. The TenantId will likely be identified by a header value or the originating domain, unless there's a more advisable approach. I've seen various