Large scale business application - Azure cloud database & storage issues -


We are making massive, database oriented business applications. This business application is the majority and we want to provide it as a SOA (software as a service) in AZUR Cloud. The blue SQL database limit is only 150 GB which is not enough for us. There is a huge amount of data in our customers, which is likely to increase every year. Our application database is relational and complex and uses complex questions (group, connects, total work), stored procedures to obtain / save data, so we are reluctant to use the Big Table directly. There is a suggestion to break the database in the database and file groups, but we are not going to do this. There is only one possibility that only the current year's data should be restored in the app and in other partitions / backup databases, but it is not in line with our application because previous data is often used. If we use the blue table, then our complex operation will be carried out in memory, which is not possible due to limited memory resources. We are thinking of mixing Azure SQL Database and Azure Table. But we are unable to find any suitable examples that use the mixture of both of us.

We are also looking for answers to the following questions?

  1. On the large scale of relational data (TB) or should we have our own database server to support it?
  2. Should we just use the blue tab and not blue SQL?
  3. Blue SQL and blue table storage? Is there any sample architecture / example that guides about it?
  4. New Standard and Premium Ezur SQL Database SKU now supports 250 GB and 500 GB Are there. Regardless, the Ezur SQL Database is a very large scale model for large amounts of data. There is a preview of an elastic scale facility for the Ezur SQL Database.

    There are good reasons to store the data in the most appropriate location - Azure Tables offers more cost-effective, higher-level storage Blue SQL database does have high-level, semi-structured data in Azure Tables And relational data in the Azure SQL database - of course there are definitely reasons to use each for data.

    1) If you are creating a new application, you should consider the AZUR SQL database for your relational data and only need to go to the SQL Server in the Ezur Virtual Machine if that will not work. While SQL Server is easy to find in a VM, once you start deployment, then things are starting after adding traditional DBA activities. If you have high-level relational requirements then you should consider making comb.

    2) Your preference should not be one or the other, but where appropriate, both of them should be used.

    3) Microsoft Pattern & amp; To help with your architecture, you should see a lot of practices in practice.


Comments

Popular posts from this blog

java - Can't add JTree to JPanel of a JInternalFrame -

javascript - data.match(var) not working it seems -

javascript - How can I pause a jQuery .each() loop, while waiting for user input? -