From 22f7c7f0e86f23c9d17cc79b7f8bb5a9d5fb85e5 Mon Sep 17 00:00:00 2001 From: CarlRabeler Date: Wed, 1 Jun 2016 10:53:34 -0700 Subject: [PATCH] pics --- .../readme.md | 22 +++++++++---------- .../azure-sql-db-elastic-pools/readme.md | 12 +++++----- 2 files changed, 17 insertions(+), 17 deletions(-) diff --git a/samples/manage/azure-sql-db-elastic-pools-custom-dashboard/readme.md b/samples/manage/azure-sql-db-elastic-pools-custom-dashboard/readme.md index f796133e45..e2615be720 100644 --- a/samples/manage/azure-sql-db-elastic-pools-custom-dashboard/readme.md +++ b/samples/manage/azure-sql-db-elastic-pools-custom-dashboard/readme.md @@ -13,12 +13,12 @@ This readme applies to: ## About this sample -- ***Applies to:*** Azure SQL Database -- *** Key features:*** Elastic Pools -- ***Workload:*** SaaS workload generator -- ***Programming Language:*** ADO.NET, XML, C#, Transact-SQL -- ***Authors:*** Zoiner Tejada, Carl Rabeler, Srini Acharya -- ***Update history:*** n/a +***Applies to:*** Azure SQL Database
+*** Key features:*** Elastic Pools
+***Workload:*** SaaS workload generator
+***Programming Language:*** ADO.NET, XML, C#, Transact-SQL
+***Authors:*** Zoiner Tejada, Carl Rabeler, Srini Acharya
+***Update history:*** n/a
## Solution Quick Start Overview @@ -50,7 +50,7 @@ Contoso Shopkeeper provides business small and mid-size an easy to use, cost-eff The fundamentals behind the architecture of ShopKeeper are resource sharing amongst tenants (which helps keep costs down for both Contoso and its merchant customers), and isolation between tenants (which aims to guarantee that one merchants code or data is never mixed in with another’s). Take the example below, where a customer is using her Web Browser to shop Fabrikam Fabrics. In the process of placing an order she would be interacting with a Web App that only contains Fabrikam Fabric’s code, and the Web App would interact with the database instance that only contains Fabrikam Fabric’s data- this is the isolation aspect. The fact that various Web Apps share the resources from an App Service Plan or that multiple SQL Databases instances share resources from an Elastic Pool demonstrates the resource sharing aspect. - @@ -60,16 +60,16 @@ The focus of this Solution Quick Start is on leveraging Elastic Pools and unders Since the best way to understand the behavior of Elastic Pools is to experience using them under load, we provide a load generator. The load generator is a console application that targets one or more elastic database instances in an Elastic Pool with a specific write load. You can run multiple instances of the load generator with different settings if you want to create a blended load, e.g., a mix of heavy a light load. In addition, you do not need to target all databases in the pool by the load generator, so you can leave databases you choose without any load. - @@ -88,7 +88,7 @@ In the ShopKeeper scenario, for example, assume Contoso has a Free Subscription So how does this map to how Contoso might leverage Elastic Pools? The database cost per tenant is effectively the cost of the pool divided by the number of tenant databases in the pool. The number of databases that can be added to any given pool is limited by the pricing tier of the pool. For example, a Standard 200 pool supports up to 400 databases. Currently this tier is priced at $446 USD per month. If Contoso were to fully utilize the pool by adding 400 databases, the cost per tenant would near $1.12 per tenant per month. Similarly, if they used the Basic 200 tier (which currently is priced at $298 USD per month), then the cost per tenant- month would near $0.75. - +***Key features:*** Elastic Pools
+***Workload:*** n/a
+***Programming Language:*** PowerShell, Transact-SQL, DAX
+***Authors:*** Carl Rabeler, Srini Acharya
+***Update history:*** n/a
### Contents