1、n managing infrastructure Monetize new offering quickly without investment in billing and other enablement technologies. Speed of development Interoperability Leverage existing IP Simplified deployment Scale up or down as business needs change Go to market faster Reliable service SLAs Security Globa
2、l data centers Lower costsEfficiency Stay Competitive Innovation Agility Generate New Revenue Quickly Reliability Reduced Risk Platform of Choice Sign up at the Windows Azure Platform developers portal Windows Azure access Developer tools White papers Sample applications Plan pilot applications, pro
3、ofs of concept, and architectural design sessions with Windows Azure partners Application Architecture Application Models Web Hosting Massive scale infrastructure Burst client request re-routed to new primary on failure High SLA guarantee using logical replication (hot standby replicas) Automatic ma
4、nagement, self-healing and load balancing across shared resource pool SQL Azure Database provides provisioning, metering and billing infrastructure Machine 5 SQL Instance SQL DB User DB1 User DB2 User DB3 User DB4 SQL Azure Database Provisioning (databases, accounts, roles, , Metering, and Billing M
5、achine 6 SQL Instance SQL DB User DB1 User DB2 User DB3 User DB4 Machine 4 SQL Instance SQL DB User DB1 User DB2 User DB3 User DB4 DBA role will change to focus on policy/logical management Security and Connection Models Connect using common client libraries ADO.NET, OLE DB, ODBC, etc. Clients conne
6、ct to a database directly Cannot hop across DBs Large surface of SQL supported within the database boundary Future work will relax many of these constraints Security Connections Uses regular SQL security model Authenticate logins, map to users and roles Authorize users and roles to SQL objects Suppo
7、rts standard SQL logins Logins are username + password strings Service enforces use of SSL to secure credentials Future support for AD Federation, WLID, etc as alternate authentication protocols Provisioning Model Account and server provisioning Portal and API based access Ex: enumerate my servers,
8、show server usage metrics, etc Each account has one or more servers Ex: Each server has a virtual master database Has subset of SQL Server master DB interface Each server has one or more SQL logins System creates sysadmin login on “server creation” Databases created using “CREATE DATABASE” Can be ca
9、lled by sysadmin or anyone with create DB permission * * SQL Server Compatibility SQL Server has many patterns for accomplishing tasks SQL Azure Database supports a subset of full SQL Server patterns Focus on logical and policy based administration Patterns work in both SQL Azure Database and SQL Se
10、rver Enables migration of on-premise application to/from SQL Azure SQL Azure Database is a multi-tenant service Throttling and load balancing policies Examples: limit on DB size, duration of transaction, In Scope for v1 Create/Alter/Drop on Database/Index/View Stored Procedures (Transact-SQL) Trigge
11、rs Constraints Table variables, session temp tables (#t) + lots of others Out of Scope for v1 CLR Service Broker Distributed Transactions Distributed Query Spatial All server level DDL All physical DDL and physical catalog views Departmental Applications Departmental workgroup applications with low
12、concurrency and cyclical usage patterns Web Applications Small customers or start ups with Web applications of all scale that have simple RDBMS needs Data Hubs Secure data hubs that consolidate multiple data sources and enable access from multiple locations and devices ISV/SaaS Offerings Traditional ISVs extending offering or selling software hosted in the cloud (including SaaS ISVs) Application Scenarios Thank you
