Manda QoP

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 c

Notes from Chris Auld's presentation at TechEd 09. Again, as with the other TechEd blogs, these are just notes that I can use to find out further information when more time is available. :) Azure: High scale application architecture Consolidate traditional IT to the cloud Move servers and apps out-house Reliable hardware in the cloud Virtualize to the cloud Manage explosive growth (scale out cloud) Scale out clouds are built around disposable hardware Reliability is built using software Scale out cloud is load balanced by default Greeness - PUE (power usage effectiveness) = Total Facility Power / IT Equipment Power. Google and Microsoft are getting around 1.10 to 1.25 PUE. Intergen server room is running at about 1.6 PUE. MS cloud offering = Windows Azure, .NET Services, SQL Azure Azure sits you above the abstraction layer (IMAGE TO GO IN HERE) Compute source (IMAGE TO GO IN HERE) Load balancer is key part of Windows Azure RoleEntryPointStart() has no return value. Always whi