Developing Dane

Update 10/2016 - This posting is better viewed in my new blog . Abstract Currently Azure SQL allows you to configure your database in one of three service tiers, i.e. Basic, Standard and Premium. The service tiers each allow you to select one of several performance levels. In all you have eight possible performance levels; Basic, S0, S1, S2, S3, P1, P2, P3. The goal of this exercise was to provide some quantification of these performance levels. Setup Test System: Azure VM with Windows Server 2012 R2 and SQL Server 2014. Database: SQL database with a complex history table (many columns) which held ~250K records. Client: SQL Server Mangment Studio (SSMS) hosted on the Test System. All test runs utilized a copy of the Database. For tests labeled "Local" the Database was hosted on the Test System. For all other tests the Database was hosted as an Azure SQL database under the labeled performance level. All queries were executed from the Client. Reported query executi...

Update 10/2016 - This posting is better viewed in my new blog . Getting my feet wet with Azure SQL tonight and I just created my first ever database on the platform. The first step was to create a new server instance since I did not yet have a hosting server. The second page of the creation prompts you to provide credentials for the new server. With no instructions about what to use as a "log in name" I used my gmail account as I would for almost any account name. The database created successfully but I quickly found I couldn't access it at all. I just kept getting authentication errors. I noticed in one of the errors that the user name reported in the failure was the login name I'd initially entered with the "@gmail.com" truncated. This made me wonder if Azure was understanding the "@" character as a domain indicator. I went back to the Azure portal, deleted the server and started from scratch creating another new server. This time around I ...