蓝色波浪ppt模板之微软SQL azure sept.pptx

Lynn Langit/SoCalDevGaltwitter - @llangit;Windows Azure Platform;Data Storage Choices;;Database Replicas;SQL Azure focus on logical administration Schema creation and management Query optimization Security management (Logins, Users, Roles) Service handles physical management Automatically replicated with HA “out of box” Transparent failover in case of failure Load balancing of data to ensure SLA;SQL Azure portal - ;Each account has zero or more servers Azure wide, provisioned in a common portal Billing instrument Each server has one or more databases Contains metadata about the databases and usage Unit of authentication Unit of Geo-location Generated DNS based name Each database has standard SQL objects Unit of consistency Unit of multi-tenancy Contains Users, Tables, Views, Indices, etc. Most granular unit of billing ;SQL AzureAccessing databases;Use ADO.NET, ODBC, PHP (NOT OLE DB) Client libraries pre-installed in Azure roles Support for ASP.NET controls Clients connect directly to a database Cannot hop across DBs (no USE) May need to include login@server Use familiar tools (sqlcmd, osql, SSMS, etc) Use connection pooling for efficiency SSMS 2008 R2 CTP can connect /ssds/archive/2009/11/11/9921041.aspx ;Connecting to SQL Azure with SSMS 2008 R2 SQL Azure Explorer for VS 2010 / SQLCMD – can also be used SSIS – can also be used SSRS/SSIS/SSAS – w/SQL Azure as source data – use R2 versions;SSMS 2008 R2 – Cloud vs. On Premise;Query Optimizer and Client Statistics can be used with SQL Azure data; Maximum single database size is 50GB Database size calculation Includes: primary replica data, objects and indexes Does NOT include: logs, master database, system tables, server catalogs or additional replicas No support for auto-partitioning or fan-out queries (yet) Must handle partitioning logic within the application Also called Database ‘sharding’ Sharding Utility, using TPL at / ;Compatibility ;Tables (joins) , Views , Stored Procedures, Triggers Indices Index Man