Sam
Sam

Reputation: 21

Dynamic Database / Schema in Entity framework on Windows Azure / SQL Azure

We are currently in process of developing SAAS application codename FinAcuity which will be hosted on Windows Azure platform and primary database will be SQL Azure.

Here are some Technical Specifications for our product:

Here is our Business Case:

Note: Table structure will be same for each Schema.

Here are some scenarios to will give you a deeper view of our application processes.

Scenario 1:

Scenario 2:

Scenario 3:

Scenario 4:

Need advice for best possible solution for each scenario that is listed above.

Thank you in advance.

Best Regards - Sahil

Upvotes: 2

Views: 1366

Answers (1)

Sandrino Di Mattia
Sandrino Di Mattia

Reputation: 24895

I think this is a little too much for 1 single question.

And I personally think you look at it from a wrong perspective. Why did you choose Entity Framework and SQL Azure? Do you really think these are the best technologies to address your problems?

I suggest you take a step back and investigate what other technologies could be used. Because what you're asking here looks like a schema-less solution, and SQL Azure / SQL Server wasn't built for that IMHO.

You can start by looking at a NoSQL (schema-less, key value store) solution, possibly in Windows Azure. There's a whitepaper that will get you started on that: NoSQL and the Windows Azure platform -- Investigation of an Unlikely Combination

Windows Azure Table Storage is a key-value store that could solve some of your issues:

  • Customer isolation / Multiple schemas: WAZ Table Storage supports partitions, you could partition your data per customer instead of putting all the data together.
  • Provisioning: No need to provision anything. Get a storage account and you can get started. Then you can simply have some code that writes data in a specific partition for that customer.
  • Cost (not mentioned in the question): Table Storage is much cheaper than SQL Azure
  • ...

Upvotes: 1

Related Questions