Building Applications on SQL Azure

-
These are my notes from Jeremy Boyd's presentation at TechEd NZ '09. These notes are pointers for finding out additional information and as such do not give full details of any particular areas of SQL Azure.

  • Initial services coming with SQL Azure - RDBMS, Data Sync, Data Hub
  • Down the road they will add more services such as Reporting Services and Analysis Services
  • Databases limited to 10GB each
  • SQL Azure is not SQL Data Services - they are two different things. SQL Data Services no longer exists and the tasks it was achieving are now part of Windows Azure.
  • SQL Azure has a familiar SQL relational model
  • Virtual DB server
  • Auto HA and fault tolerance
  • Friction-free scaling
  • Self provisioning
  • Provisioning model: Create an account, add a server, add a database, connect & play OR you can create via SSMS
  • All standard T-SQL language minus a lot of DBA stuff
  • When connecting ignore the error message - it's irrelevant and doesn't stop you connecting.
  • All tables MUST have a clustered index on SQL Azure
  • Can target SQL Azure either remotely from on-premise application, from an application on Windows Azure (fastest option), or alternatively use SQL Azure for storage.
  • V1 of SQL Azure does not support partitioning, so use sharding. Sharding is where you use several databases to store portions of the data. Same schema used across all databases.
  • SQL Azure is currently in CTP1 with CTP2 due soon with better tooling
  • Free to use until launch date sometime in November 2009 - so get playing
  • Check it out at http://connect.microsoft.com
The following items are missing:
  • CLR
  • DB File Placement
  • DB Mirroring
  • Distributed queries
  • Distributed transactions
  • Filegroup management
  • Full text search
  • Global temp tables
  • Spatial data & indexes
  • SQL Server config options
  • SQL Server service broker
  • System tables
  • Trace flags and quite a few other items
  • Check MSDN for command by command break down of what is and isn't supported.
Migrating an existing DB to SQL Azure
  • ANSI_NULLS not supported
  • PAD_INDEX not supported
  • Can't specify row locks
  • Can't specify filegroup reference or partitioning
  • Codeplex project which copes with this and updates your script: SQL Azure Migration Wizard
  • Check all tables have clustered index before migrating (codeplex tool will do this)
  • Should be able to migrate DB without too many hassles
On-premise scenario
  • Data is located outside the firewall from where the app runs
  • In NZ we need to be espcially vigilant about handling latency
  • Expect poor latency when using the on-premise scenario and factor caching into the design of your application
  • Favour chunky calls rather than chatty calls
  • When caching, don't hold on to the data so long that it becomes stale, use query notifications - if data changes, update cache
Better option
  • Build an app - deploy to Windows Azure with SQL Azure as the backend
  • This gives you a lower latency, however, as good programming practice, you should still factor caching into the design of your app
Synchronization
  • SQL Azure - great data sync point
  • High Availability
  • Scaleable
  • Sync framework = Project Huron
  • Mobile device access can make good use of synchronization
  • Project Huron - only available server side at the moment, client side bits coming soon
Database size 10GB
  • Includes: Primary replica data, objects and indexes
  • Does NOT include: Logs, masterdb, system tables, server catalogues, additional replicas
More info
  • More info on up coming project additions: http://www.microsoft.com/azure/sqllabs.mspx
  • http://blogs.msdn.com/ssds
  • To sign up for the CTP: http://msdn.microsoft.com/en-us/sqlserver/dataservices/default.aspx

Comments

Post a Comment

Popular posts from this blog

Yay - It works! Rebuild/Reorganize all indexes in one go - woo hoo

-
/*Version 1 of my script to fix all fragged indexes on a database */ /*Must be logged in as [sa] for this to work, if not, you will get permissions errors*/ /*You should be able to copy and paste this script in its entirity to your SQL 2005 or higher query window and run it without altering anything other than the USE .*/ /*Perform a 'USE ' to select the database in which to run the script.*/ USE AdventureWorks GO -- Make sure temp table doesn't exist IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[tmp_fraglist]') AND type in (N'U')) DROP TABLE [dbo].[tmp_fraglist] GO -- Declare variables SET NOCOUNT ON DECLARE @tablename NVARCHAR (255) DECLARE @indexname NVARCHAR (255) DECLARE @indextype NVARCHAR (255) DECLARE @execstr NVARCHAR (255) DECLARE @pagecounts INT DECLARE @frag DECIMAL DECLARE @reorgFragSize DECIMAL DECLARE @rebldFragSize DECIMAL DECLARE @numrecords INT DECLARE @rowcount INT DECLARE @errorMessage
Read more

The Grace Jones

-
Well, we finished recording the CD and now all the hard work is starting, the editing, mixing, production etc... We've also got some guys working on a video for us which sounds as though it's going to be interesting. Time to sell the house in order to pay for the tour of Ireland next year I guess. :)
Read more

What is a geek?

-
Someone raised an interesting point on Monday night at a GGD dinner and I feel they have missed the entire point of Girl Geek Dinners and have also, with their comments, seriously undermined other women who are looking to come out of their shell and interact with other 'geeks'. If you don't agree with what we're doing then don't come to a Girl GEEK dinner, and certainly don't turn up and throw cold water on people, make belittling comments and then moan that it was too technical and you didn't enjoy it. So what is a geek? There seemed to be some confusion. These women throwing around the derogatory comments seem especially confused. So let's refresh everyones' minds. You don't need to be in IT to be a geek folks! It's not an exclusive club limited to women who don't baulk at the thought of writing code. We're a diverse crowd and we celebrate each others geekiness, even if it isn't something we're into. We certainly
Read more