Hello All,

Can you please let me know what bandwidth and other configuration I should use if I want to use 2GB database on Microsoft Azure.

Are you talking about running SQL on a VM or using the Azure SQL database service? Either way that's a very small database so throughput is not likely going to be a concern with typical IO patterns (80% read, 20% write, 90% random, 8K IO size).

If your database never gets larger than 2GB, then the "Basic" service tier with 5 DTUs (database throughput units) might be a good place to start. If your DB might grow larger than 2GB or you need a little more horsepower you can upgrade to the "Standard" service with 10 DTUs.

These are just starting points. Every application/transaction workload is different and varies. The best thing is to start small as suggested and monitor your performance. If you encounter performance issues (high latency, etc...) then you can just upgrade your DTUs or service tier.

-Robert

 

• Proposed as answer by Robert McDermott Thursday, February 26, 2015 5:25 PM

Are you talking about running SQL on a VM or using the Azure SQL database service? Either way that's a very small database so throughput is not likely going to be a concern with typical IO patterns (80% read, 20% write, 90% random, 8K IO size).

If your database never gets larger than 2GB, then the "Basic" service tier with 5 DTUs (database throughput units) might be a good place to start. If your DB might grow larger than 2GB or you need a little more horsepower you can upgrade to the "Standard" service with 10 DTUs.

These are just starting points. Every application/transaction workload is different and varies. The best thing is to start small as suggested and monitor your performance. If you encounter performance issues (high latency, etc...) then you can just upgrade your DTUs or service tier.

-Robert

 

• Proposed as answer by Robert McDermott Thursday, February 26, 2015 5:25 PM

Are you talking about running SQL on a VM or using the Azure SQL database service? Either way that's a very small database so throughput is not likely going to be a concern with typical IO patterns (80% read, 20% write, 90% random, 8K IO size).

If your database never gets larger than 2GB, then the "Basic" service tier with 5 DTUs (database throughput units) might be a good place to start. If your DB might grow larger than 2GB or you need a little more horsepower you can upgrade to the "Standard" service with 10 DTUs.

These are just starting points. Every application/transaction workload is different and varies. The best thing is to start small as suggested and monitor your performance. If you encounter performance issues (high latency, etc...) then you can just upgrade your DTUs or service tier.

-Robert

 

• Proposed as answer by Robert McDermott Thursday, February 26, 2015 5:25 PM
• Marked as answer by Eric__ZhangMicrosoft contingent staff, Moderator 22 hours 9 minutes ago

Are you talking about running SQL on a VM or using the Azure SQL database service? Either way that's a very small database so throughput is not likely going to be a concern with typical IO patterns (80% read, 20% write, 90% random, 8K IO size).

If your database never gets larger than 2GB, then the "Basic" service tier with 5 DTUs (database throughput units) might be a good place to start. If your DB might grow larger than 2GB or you need a little more horsepower you can upgrade to the "Standard" service with 10 DTUs.

These are just starting points. Every application/transaction workload is different and varies. The best thing is to start small as suggested and monitor your performance. If you encounter performance issues (high latency, etc...) then you can just upgrade your DTUs or service tier.

-Robert

 

• Proposed as answer by Robert McDermott Thursday, February 26, 2015 5:25 PM
• Marked as answer by Eric__ZhangMicrosoft contingent staff, Moderator Tuesday, March 10, 2015 8:58 AM

Are you talking about running SQL on a VM or using the Azure SQL database service? Either way that's a very small database so throughput is not likely going to be a concern with typical IO patterns (80% read, 20% write, 90% random, 8K IO size).

If your database never gets larger than 2GB, then the "Basic" service tier with 5 DTUs (database throughput units) might be a good place to start. If your DB might grow larger than 2GB or you need a little more horsepower you can upgrade to the "Standard" service with 10 DTUs.

These are just starting points. Every application/transaction workload is different and varies. The best thing is to start small as suggested and monitor your performance. If you encounter performance issues (high latency, etc...) then you can just upgrade your DTUs or service tier.

-Robert

 

• Proposed as answer by Robert McDermott Thursday, February 26, 2015 5:25 PM
• Marked as answer by Eric__ZhangMicrosoft contingent staff, Moderator Tuesday, March 10, 2015 8:58 AM