Real World Sql Azure
•Download as PPTX, PDF•
1 like•369 views
James Johnson is the founder and president of the Inland Empire .NET User's Group and a Microsoft MVP. He is an evangelist, software architect, author, and mentor with interests in new technologies. SQL Azure is Microsoft's cloud-based relational database that is compatible with SQL Server and accessible from many programming languages. It has limitations compared to SQL Server, such as a maximum database size of 10GB and lack of features like CLR, filegroups and replication. Migration tools can help modify schemas and scripts to be compatible with SQL Azure.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Real World Sql Azure
Similar to Real World Sql Azure (20)
Recently uploaded
Recently uploaded (20)
Real World Sql Azure
- 1. Real World SQL Azure …and some other nifty stuff James Johnson Founder and President, Inland Empire .NET User’s Group Microsoft MVP e: james@iedotnetug.org t:@latringo www.duringlunch.com
- 2. Founder and President of the Inland Empire .NET User’s Group Microsoft MVP, Evangelist, Influencer, Software and Database Architect, Author, Coach, Facilitator, and Mentor ADHD/ADD/OCD when it comes to new technology Can’t stay away from the shiny new stuff. Email: james@iedotnetug.org Blog: www.duringlunch.com Twitter: @latringo Who am I?
- 3. Familiar SQL Server relational model Uses existing APIs & tools Friction free provisioning and reduced management Built for the Cloud with availability and scale Accessible to all from PHP, Ruby, and Java What is SQL Azure
- 4. Maximum single database size is currently 10GB Database size calculation Includes: primary replica data, objects and indexes Does NOT include: logs, master database, system tables, server catalogs or additional replicas V1 does not support auto-partitioning or fan-out queries Must handle partitioning logic within the application Special ConsiderationsDatabase Size
- 5. Support common application patterns Logical/policy based administration Patterns work from SQL Server to SQL Azure Multi-tenancy considerations Throttling and load balancing Limits on DB size, transaction duration Compatibility Goals
- 7. Requires clustered index
- 9. Triggers
- 10. Constraints
- 13. CLR
- 14. Service Broker
- 15. Spatial
- 17. Tables, joins, and table vars
- 18. T-SQL elements
- 21. Create/alter/drop users and logins
- 23. Spatial data and indexes
- 24. SQL Server configuration options
- 25. SQL Server Service Broker
- 26. System tables
- 28. Connecting to SQL Azure with SSMS 2008 R2 Demo
- 32. USE DATABASE
- 35. Windows logins
- 37. Indices need to be clustered
- 38. Full list at
- 40. The SQL team is working on the issue In the meantime… SQL Azure Migration Wizard http://sqlazuremw.codeplex.com Ugh… that wasn’t pretty
- 41. Using SQL Azure Migration Wizard Demo
- 42. Questions
- 43. James Johnson Email: james@iedotnetug.org Blog: www.duringlunch.com Twitter: @latringo Don’t forget to tip your wait staff Thank you
Editor's Notes
- Fan out queries: where a query can be run against every container in parallel and the results returned and a union-all performed at the client. This is an important scenario for us and we are looking at how we can make this pattern run effiAuto partitioning. Multi-spindle storage solution. 10 drives look like 1 logical drive.
- Here is my "current" take: In a pure multi-tenant architecture a single instance of the hosted application is capable of servicing all customers (tenants). Unlike more classical web applications or web services “in the cloud” which behave the same way for each requests, a multi-tenant architecture is designed to allow tenant-specific configurations at the UI (branding), business rules, business processes and data model layers. This is has to be enabled without changing the code as the same code is shared by all tenants, therefore transforming customization of software into configuration of softwre. As you can imagine, this drives the clear need for "metadata driven everything". The other main challenge is being able to co-locate (mingle and “de-mingle”) persistent data of multiple tenants in the same data infrastructure. In other words, the challenge for the multi-tenant application is to behave as if it was fully dedicated to a single tenant but is actually serving all of them in parallel on the same code base. I call this "you are my #1 customer" approach; which means every customer believe they are the #1 customer but in reality they are all served by a talented customer rep.http://blogs.msdn.com/gianpaolo/archive/2006/02/26/539717.aspx
- Clustered indexes sort and store the data rows in the table based on their key values. There can only be one clustered index per table, because the data rows themselves can only be sorted in one order. For more information about clustered index architectureWith few exceptions, every table should have a clustered index defined on the column, or columns, that offer the following: Can be used for frequently used queries. Provide a high degree of uniqueness. Can be used in range queries.Distributed Query – reference multiple linked servers and can perform either updae or read operations against each individual linked serverDistributed transactions span two or more servers known as resource managers. The management of the transaction must be coordinated between the resource managers by a server component called a transaction manager.DDL – data definition language statement to create drop or alter mining models and multidimensional objects such as cubes and dimensions
- Database files can be grouped together in filegroups for allocation and administration purposes. Some systems can improve their performance by controlling the placement of data and indexes onto specific disk drives. Filegroups can aid this process. The system administrator can create filegroups for each disk drive, then assign specific tables, indexes, or the text, ntext, or image data from a table, to specific filegroups.
- mw1c22vaga.database.windows.netjamesLatringo09!IEDOTNET_StudyGroups.StudentsSELECT ToCreate DB. Right click, New DatabaseNew TableCREATE TABLE [dbo].[MyTable]( [Id] [int] IDENTITY(1,1) NOT NULL, [FName][nvarchar] (50) NOT NULL, [LName][nvarchar] (50) NOT NULL CONSTRAINT PK_MyTable PRIMARY KEY ([Id] ASC))GO