Vertical Partitioning in SQL Azure: Part 1

re: Vertical Partitioning in SQL Azure: Part 1

Chris Auld — Thu, 08 Jul 2010 08:00:51 GMT

A couple of quick notes

The TicketDirect app uses horizontal partitioning to scale out.

Bascially it creates lots of partitions for the high load period and then consolidates them again when demand has subsided

This biggest reason for verticaly partitioning in SQL Azure is to pull the large content (binary and big text) out of SQL Azure and stick it in Windows Azure Storage.

re: Vertical Partitioning in SQL Azure: Part 1

anon — Thu, 27 May 2010 17:40:38 GMT

What are you doing to make it easier to have a single Entity Data Model that is composed of multiple physical SQL Azure Databases?

re: Vertical Partitioning in SQL Azure: Part 1

Wayne Walter Berry — Wed, 26 May 2010 20:37:46 GMT

Chris,

There are many things that we will be implementing in the future to make this particular scenario easier. We are just getting started. The code above is one intern solution to this issue.

re: Vertical Partitioning in SQL Azure: Part 1

Chris Adkin — Tue, 25 May 2010 19:18:40 GMT

Its a shame that SQL Azure does not yet support service broker and distributed partition views. You could use your first database to contains your map, always connect to this, service broker would then distribute the data across your databases and then dpvs would present a consolidated view of it all. This would minimise the amount of coding you would have to carry out in the tier above the database in order to achieve the same result.