More Related Content


Real World Sql Azure

  1. Requires clustered index
  2. Stored Procedures
  3. Triggers
  4. Constraints
  5. Distributed Query
  6. CLR
  7. Service Broker
  8. Spatial
  9. Tables, joins, and table vars
  10. T-SQL elements
  11. Create/drop databases
  12. Create/alter/drop tables
  13. Create/alter/drop users and logins
  14. Spatial data and indexes
  15. SQL Server configuration options
  16. SQL Server Service Broker
  17. System tables
  18. Specifying Filegroups
  19. Extended Properties
  22. Various Index options
  23. Windows logins
  24. Unsupported XML features
  25. Indices need to be clustered
  26. Full list at

Editor's Notes

  1. 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.
  2. 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.
  3. 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
  4. 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.
  5.!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