Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

First round of Stringy test result fixes

  • Loading branch information...
commit 552f4b848af330ec76f5d4671b8f67d79c7fdece 1 parent 21c8a14
@tysonn tysonn authored
View
2  GettingStarted/how_to_sample.md
@@ -111,7 +111,7 @@ A CloudBlobClient object lets you get reference objects for containers and blobs
// Create the blob client
CloudBlobClient blobClient = storageAccount.createCloudBlobClient();
-All blobs reside in a container. Use the **CloudBlobClient** object to get a reference to the container you want to use. You can create the container if it doesn’t exist with the **createIfNotExist** method, which will otherwise return the existing container. By default, the new container is private, so you must specify your storage account key (as you did above) to download blobs from this container.
+All blobs reside in a container. Use the **CloudBlobClient** object to get a reference to the container you want to use. You can create the container if it doesn’t exist with the **createIfNotExist** method, which will otherwise return the existing container. By default, the new container is private, so you must specify your storage access key (as you did above) to download blobs from this container.
// Get a reference to a container
// The container name must be lower case
View
2  GettingStarted/tutorial_sample.md
@@ -58,7 +58,7 @@ To get started with a free account, click free trial in the upper right corner a
The next step is to create a service namespace, and to obtain a shared secret key. A service namespace provides an application boundary for each application exposed through Service Bus. A shared secret key is automatically generated by the system when a service namespace is created. The combination of service namespace and shared secret key provides a credential for Service Bus to authenticate access to an application.
-1. Log into the Windows Azure Platform Management Portal.
+1. Log into the Windows Azure Management Portal.
2. In the lower left navigation pane of the Management Portal, click **Service Bus, Access Control & Caching**.
3. In the upper left pane of the Management Portal, click the **Service Bus** node, then click **New**.
![Management Portal New Service Bus][Image8]
View
6 ITPro/Linux/CommonTasks/commontask-create-mgt-cert.md
@@ -9,7 +9,7 @@ There is already documentation on how to create and manage these certificates at
##Table of Contents##
* [How to: Create and upload a management certificate](#createcert)
-* [How to: Create a management certificate using the Windows Azure Platform Management Portal](#silverlight)
+* [How to: Create a management certificate using the Windows Azure Management Portal](#silverlight)
<h2 id="createcert">How to: Create and upload a management certificate</h2>
@@ -77,11 +77,11 @@ Generating a new cert is not enough since all 10 certificates are valid and your
At some point after preview you will be able to use the new portal to get access to all the management cert functionality.
-<h2 id="servicemanagement">How to: Create a management certificate using the Windows Azure Platform Management Portal</h2>
+<h2 id="servicemanagement">How to: Create a management certificate using the Windows Azure Management Portal</h2>
You can read more on how to create the certificate at [http://msdn.microsoft.com/en-us/library/windowsazure/gg551721.aspx](http://msdn.microsoft.com/en-us/library/windowsazure/gg551721.aspx) or you can also use OpenSSL to create the management certificate. For more information, see [OpenSSL](http://openssl.org). After you create the certificate, you must add it to your subscription in Windows Azure.
-1. Sign in to the Windows Azure Platform Management Portal.
+1. Sign in to the Windows Azure Management Portal.
2. In the upper-left corner of the Management Portal, click **Preview**, and then click **Previous Management Portal**.
![preview](../media/preview.png)
View
4 ITPro/Linux/Fundamentals/intro-to-linux.md
@@ -50,7 +50,7 @@ The user account that is specified during virtual machine instance deployment on
<h2 id="firewallconfiguration"> Firewall Configuration </h2>
-The Windows Azure platform provides an inbound packet filter that restricts connectivity to ports specified in the Management Portal. By default, the only allowed port is SSH. You may open up access to additional ports on your Linux virtual machine by adding rules in the Management Portal.
+Windows Azure provides an inbound packet filter that restricts connectivity to ports specified in the Management Portal. By default, the only allowed port is SSH. You may open up access to additional ports on your Linux virtual machine by adding rules in the Management Portal.
The Linux images in the Windows Azure gallery do not enable the iptables firewall inside the Linux virtual machines. If desired, the IPtables firewall may be configured to provide additional capabilities.
@@ -60,7 +60,7 @@ When you initially deploy an instance of a Linux image, you are required to prov
<h2 id="virtualmachine"> Virtual Machine Image Capture </h2>
-The Windows Azure platform provides the ability to capture the state of an existing virtual machine into an image that can be subsequently be used to deploy additional virtual machine instances. The Windows Azure Linux Agent may be used to rollback some of the customization that was performed during the provisioning process. You may follow the steps below to capture a virtual machine as an image:
+Windows Azure provides the ability to capture the state of an existing virtual machine into an image that can be subsequently be used to deploy additional virtual machine instances. The Windows Azure Linux Agent may be used to rollback some of the customization that was performed during the provisioning process. You may follow the steps below to capture a virtual machine as an image:
1. Run **waagent -deprovision** to undo provisioning customization. Or **waagent -deprovision+user** to optionally, delete the user account specified during provisioning and all associated data.
View
2  ITPro/Linux/HowTo/howto-prepare-linux-distribution.md
@@ -182,7 +182,7 @@ All of your VHDs for the OS must have sizes that are multiples of 1 MB.
2. Install Opensuse 12.1 64 bit. We recommend not creating a SWAP partition at installation time. SWAP space may be configured using the Windows Azure Linux Agent.
3. Update to latest kernel:
- **Note:** As of today the SLES kernel update doesn’t have and important fix on the kernel to improve storage performance and we expect it to land shortly after release. We recommend that you use an Azure image from the [http://www.susestudio.com](http://susestudio.com/) gallery to take advantage of all the functionality in azure
+ **Note:** As of today the SLES kernel update doesn’t have and important fix on the kernel to improve storage performance and we expect it to land shortly after release. We recommend that you use a Windows Azure image from the [http://www.susestudio.com](http://susestudio.com/) gallery to take advantage of all the functionality in azure
4. Disable legacy ATA driver by adding the following to kernel command line in /boot/grub/menu.lst: reserve=0x1f0, 0x8.
(This option reserves this I/O region and prevents ata_piix from loading)
View
2  ITPro/Linux/HowTo/howto-servicemgt-api.md
@@ -103,7 +103,7 @@ Note that in some cases completion may only indicate that the request was accept
- serviceName is a required string name of the hosted service.
- callback is required.
-- The response object will contain storage account keys if successful.
+- The response object will contain storage access keys if successful.
**iaasClient.GetDeployment(serviceName, deploymentName, callback)**
View
8 ITPro/Shared/Chunks/win-az-command-line-tools.md
@@ -139,7 +139,7 @@ List Azure virtual machines
###vm show [options] &lt;name>
-Show details about an Azure virtual machine
+Show details about a Windows Azure virtual machine
~$ azure vm show my-vm
info: Executing command vm show
@@ -304,7 +304,7 @@ Data disks are .vhd files in blob storage that can be used by a virtual machine.
###vm disk show [options] &lt;name>
-Show details about an Azure disk
+Show details about a Windows Azure disk
~$ azure vm disk show my-vm-my-vm-2-201242418259
info: Executing command vm disk show
@@ -363,7 +363,7 @@ This command attaches an existing disk in blob storage to an existing virtual ma
###vm disk attach-new &lt;vm-name> &lt;size-in-gb> [blob-url]
-Attaches data-disk to Azure virtual machine
+Attaches a data-disk to a Windows Azure virtual machine
~$ azure vm disk attach-new nick-test36 20 http://nghinazz.blob.core.azure-preview.com/vhds/vmdisk1.vhd
info: Executing command vm disk attach-new
@@ -371,7 +371,7 @@ Attaches data-disk to Azure virtual machine
###vm disk detach &lt;vm-name> &lt;lun>
-Detaches a data-disk attached to an Azure virtual machine
+Detaches a data-disk attached to a Windows Azure virtual machine
~$ azure vm disk detach my-vm 2
info: Executing command vm disk detach
View
6 Shared/Chunks/SecurityRX.md
@@ -2,7 +2,7 @@
##Abstract
-When developing applications for the Windows Azure platform identity and
+When developing applications for Windows Azure, identity and
access are the primary security concerns that you need to keep in mind.
This topic explains the key security concerns in the cloud and how you
can best protect your application.
@@ -21,7 +21,7 @@ hand, the cloud intrinsically exposes more surface area for your
application that can be potentially exploited by attackers. This is
because many cloud technologies and services are exposed as end points
vs. in-memory components. Windows Azure storage, Service Bus, SQL
-Database (formerly SQL Azure), and many other services are accessible
+Database, and many other services are accessible
via their endpoints over the wire.
In cloud applications more responsibility lays on the shoulders of the
@@ -112,7 +112,7 @@ app's identity and access implementation:
- Do you store Windows Azure services credentials in clear?
- Do your Windows Azure services credentials follow strong password
policies?
-- Do you rely on the Windows Azure platform to verify credentials vs.
+- Do you rely on Windows Azure to verify credentials vs.
using custom verification mechanisms?
- Do you limit Windows Azure services authentication sessions or token
lifetime to a reasonable time window?
View
92 Shared/Chunks/create-and-configure-sql-database.md
@@ -1,11 +1,11 @@
-## <a name="create-sql"> </a>Create a SQL Azure Server
+## <a name="create-sql"> </a>Create a SQL Database Server
-Before you can use SQL Azure, you must first create a Windows Azure
+Before you can use SQL Database, you must first create a Windows Azure
account, which allows you to access all the Windows Azure services,
-including SQL Azure. For information, see [Windows Azure Free Trial][].
+including SQL Database. For information, see [Windows Azure Free Trial][].
After you have signed up, you can use Windows Azure Management Portal to
-create and manage your SQL Azure server.
+create and manage your SQL Database server.
1. Log into the [Windows Azure Management Portal][].
2. In the navigation pane on the left, click **Database**.
@@ -15,39 +15,39 @@ create and manage your SQL Azure server.
![][0]
-3. Select a region in which you want to host your SQL Azure server, and
+3. Select a region in which you want to host your SQL Database server, and
then click **Next**. Typically, you want to choose a region that is
closer to your location to reduce network latency.
4. Type the Administrator login name and the password, and then click
**Next**.
- **Note:** SQL Azure only supports SQL Authentication; Windows
+ **Note:** SQL Database only supports SQL Authentication; Windows
authentication is not supported.
5. Click **Finish**. You will configure the firewall rules in the
- [Configure Access to the SQL Azure Server][] section.
+ <a href="#config-access">Configure Access to the SQL Database Server</a> section.
6. In the navigation pane, expand the subscription in which you created
- the database server, and then click the newly created SQL Azure
+ the database server, and then click the newly created SQL Database
server.
![][1]
In the Properties pane on the right, it lists the Fully Qualified
- DNS Name (FQDN) and other properties of the SQL Azure server. You
+ DNS Name (FQDN) and other properties of the SQL Database server. You
will need the FQDN to build your connection string. In the middle
pane, it lists the master database that is created when the SQL
Azure server is created.
- **Note:** Because the SQL Azure server must be accessible worldwide,
- SQL Azure configures the appropriate DNS entries when the server is
+ **Note:** Because the SQL Database server must be accessible worldwide,
+ SQL Database configures the appropriate DNS entries when the server is
created. The generated name ensures that there are no name
collisions with other DNS entries. You cannot change the name of
- your SQL Azure server.
+ your SQL Database server.
-For more information, see [How to Create a SQL Azure Server][]. Next,
-configure access to the SQL Azure server by creating firewall rules.
+For more information, see [How to Create a SQL Database Server][]. Next,
+configure access to the SQL Database server by creating firewall rules.
-## <a name="config-access"> </a>Configure Access to the SQL Azure Server
+## <a name="config-access"> </a>Configure Access to the SQL Database Server
-SQL Azure firewall prevents all access to your SQL Azure server until
+SQL Database firewall prevents all access to your SQL Database server until
you specify which computers and services have permission to access it.
The firewall grants access based on the originating IP address of each
request. You must create firewall rules to allow access from the client
@@ -55,15 +55,15 @@ computers, including your development computer so you can test your
application.
1. At the top of the navigation pane, expand **Subscriptions**, expand
- the subscription, and then click the SQL Azure server you created in
+ the subscription, and then click the SQL Database server you created in
the previous procedure.
2. In the middle pane, click **Firewall Rules**.
3. Select **Allow other Windows Azure services to access this server**.
A firewall rule called MicrosoftServices is added to the firewall
rule list by default. This setting enables other Windows Azure
- services including [Management Portal for SQL Azure][] to access the
- SQL Azure server. You will use the Management Portal for SQL Azure
- in the [Create a SQL Azure Database][] section.
+ services including [Management Portal for SQL Database][] to access the
+ SQL Database server. You will use the Management Portal for SQL Database
+ in the [Create a SQL Database Instance][] section.
4. Click **Add** to create another firewall rule.
5. Enter a rule name, and an IP range, and then click **OK**. The rule
name must be unique. The IP address of your computer is listed on
@@ -73,16 +73,16 @@ application.
Note: There can be up as much as a five-minute delay for changes to
the firewall settings to take effect.
-The SQL Azure Database service is only available with TCP port 1433 used
+The SQL Database service is only available with TCP port 1433 used
by the TDS protocol, so make sure that the firewall on your network and
local computer allows outgoing TCP communication on port 1433. For more
-information, see [SQL Azure Firewall][].
+information, see [SQL Database Firewall][].
-## <a name="create-db"> </a>Create a SQL Azure Database
+## <a name="create-db"> </a>Create a SQL Database Instance
-To create a new database, you must connect to the master database. The
-following steps show you how to create a database using the Management
-Portal for SQL Azure.
+To create a new instance, you must connect to the master instance. The
+following steps show you how to create an instance using the Management
+Portal for SQL Database.
1. At the top of the navigation pane, expand **Subscriptions**, expand
the subscription, expand the SQL Azure server you created, click
@@ -90,24 +90,24 @@ Portal for SQL Azure.
![][2]
- This opens the Management Portal for SQL Azure logon screen.
+ This opens the Management Portal for SQL Database logon screen.
![][3]
2. Enter the user name and the password that you specified when you
- created the SQL Azure server, and then click **Log on**. This opens
- the Management Portal for SQL Azure in a different browser tab or a
+ created the SQL Database server, and then click **Log on**. This opens
+ the Management Portal for SQL Database in a different browser tab or a
new browser window.
**Note:** If an error occurs, it displays a message saying "There
was an error connecting to the server" beneath the Password textbox.
You can click on the message to see the error details. A common
error is the firewall rule not created for the client computer.
-3. In the Management Portal for SQL Azure, click **New Query**. ![][4]
+3. In the Management Portal for SQL Database, click **New Query**. ![][4]
4. In the query window, copy and paste the following Transact-SQL
- script using your own name for the database in place of
- database\_name:
+ script using your own name for the instance in place of
+ instance\_name:
- CREATE DATABASE database_name;
+ CREATE DATABASE instance_name;
5. Click **Execute**. Make sure the result pane showing **Command(s)
completed successfully.**
@@ -117,7 +117,7 @@ Portal for SQL Azure.
8. From the View ribbon, click **Refresh**. The new database is listed
in the navigation pane.
-SQL Azure Database provides two database editions:
+SQL Database provides two database editions:
- Web Edition - Grows up to a size of 5 GB
- Business Edition - Grows up to a size of 50 GB.
@@ -127,27 +127,27 @@ later be changed using ALTER DATABASE. MAXSIZE provides the ability to
limit the size of the database.
You can also use SQL Server Management Studio 2008 R2 (SSMS) to create a
-SQL Azure database. For a list of supported tools and utilities, see
-[Tools and Utilities Support (SQL Azure Database)][]. For more
-information on creating SQL Azure database, see [How to Create a SQL
-Azure database][].
+SQL Database instance. For a list of supported tools and utilities, see
+[Tools and Utilities Support (SQL Database)][]. For more
+information on creating SQL Database instances, see [How to Create a SQL
+Database Instance].
-For each database created on SQL Azure, there are actually three
+For each instance created on SQL Database, there are actually three
replicas of that database. This is done to ensure high availability.
Failover is transparent and part of the service. The [Service Level
-Agreement][] provides 99.9% uptime for SQL Azure.
+Agreement] provides 99.9% uptime for SQL Database.
[Windows Azure Free Trial]: {localLink:2187} "Free Trial"
[Windows Azure Management Portal]: http://windows.azure.com
[0]: ../../DevCenter/dotNet/Media/sql-01.png
[1]: ../../DevCenter/dotNet/Media/sql-02.png
- [How to Create a SQL Azure Server]: http://social.technet.microsoft.com/wiki/contents/articles/how-to-create-a-sql-azure-server.aspx
- [Management Portal for SQL Azure]: http://msdn.microsoft.com/en-us/library/windowsazure/gg442309.aspx
- [SQL Azure Firewall]: http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-firewall.aspx
+ [How to Create a SQL Database Server]: http://social.technet.microsoft.com/wiki/contents/articles/how-to-create-a-sql-azure-server.aspx
+ [Management Portal for SQL Database]: http://msdn.microsoft.com/en-us/library/windowsazure/gg442309.aspx
+ [SQL Database Firewall]: http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-firewall.aspx
[2]: ../../DevCenter/dotNet/Media/sql-03.png
[3]: ../../DevCenter/dotNet/Media/sql-04.png
[4]: ../../DevCenter/dotNet/Media/sql-05.png
- [Tools and Utilities Support (SQL Azure Database)]: http://msdn.microsoft.com/en-us/library/windowsazure/ee621784.aspx
- [How to Create a SQL Azure database]: http://social.technet.microsoft.com/wiki/contents/articles/how-to-create-a-sql-azure-database.aspx
+ [Tools and Utilities Support (SQL Database)]: http://msdn.microsoft.com/en-us/library/windowsazure/ee621784.aspx
+ [How to Create a SQL Database Instance]: http://social.technet.microsoft.com/wiki/contents/articles/how-to-create-a-sql-azure-database.aspx
[Service Level Agreement]: {localLink:1132} "SLA"
- [How to Create a SQL Azure database]: http://social.technet.microsoft.com/wiki/contents/articles/how-to-create-a-sql-azure-database.aspx
+ [How to Create a SQL Database Instance]: http://social.technet.microsoft.com/wiki/contents/articles/how-to-create-a-sql-azure-database.aspx
View
50 Shared/Chunks/performance.md
@@ -83,15 +83,15 @@ One common design pattern where you can consider Table Storage involves a table
For more discussion of Table Storage, see:
* [Azure Table Storage Performance Considerations](http://go.microsoft.com/fwlink/?LinkId=252663).
-* [SQL Azure and Windows Azure Table Storage](http://go.microsoft.com/fwlink/?LinkId=252664)
+* [SQL Database and Windows Azure Table Storage](http://go.microsoft.com/fwlink/?LinkId=252664)
* [Improving Performance by Batching Azure Table Storage Inserts](http://go.microsoft.com/fwlink/?LinkID=252665), which discusses some performance results.
-* [SQL Azure Performance and Elasticity Guide](http://go.microsoft.com/fwlink/?LinkId=221876)
+* [SQL Database Performance and Elasticity Guide](http://go.microsoft.com/fwlink/?LinkId=221876)
#### Data Partitioning ####
-One of the most frequently partitioned resources is data. If you are creating a Windows Azure Cloud Service, then you should consider the use of SQL Azure’s built-in sharding available via Federations. Be sure to build a proof of concept to determine that Federations provides the needed partitioning for your application.
+One of the most frequently partitioned resources is data. If you are creating a Windows Azure Cloud Service, then you should consider the use of SQL Database’s built-in sharding available via Federations. Be sure to build a proof of concept to determine that Federations provides the needed partitioning for your application.
-If SQL Azure Federations does not meet your scalability requirements, there are numerous examples of “do-it-yourself” partitioning that you can consider adopting.
+If SQL Database Federations does not meet your scalability requirements, there are numerous examples of “do-it-yourself” partitioning that you can consider adopting.
##### Federations Limitations and Scalability Tradeoffs #####
@@ -101,16 +101,16 @@ Federations is easiest to implement for new development, and for existing applic
Your “proof of concept” application may encounter limitations in Federations ability to scale. When you partition a group of tables, rows that contain a key within a specified range occupy one of a number of Federation members, each of which is a separate database. Currently Federations scales well up to about 6 federation members. If you require more partitions, you may wish to consider “do-it-yourself” partitioning.
-Another major trade off is that the transaction model becomes that of “eventual consistency”, because each Federation member is a separate database, and SQL Azure does not support cross-database joins.
+Another major trade off is that the transaction model becomes that of “eventual consistency”, because each Federation member is a separate database, and SQL Database does not support cross-database joins.
-One consequence of this is that if you need to do a fan-out query that crosses federation member boundaries (for example, get all Orders made this month), you will need to use logic in the application layer to support it. This blog post describes the basics of doing this: [Introduction to Fan-out Queries for Federations in SQL Azure (Part 1): Scalable Queries over Multiple Federation Members, MapReduce Style!](http://go.microsoft.com/fwlink/?LinkID=252667)
+One consequence of this is that if you need to do a fan-out query that crosses federation member boundaries (for example, get all Orders made this month), you will need to use logic in the application layer to support it. This blog post describes the basics of doing this: [Introduction to Fan-out Queries for Federations in SQL Database (Part 1): Scalable Queries over Multiple Federation Members, MapReduce Style!](http://go.microsoft.com/fwlink/?LinkID=252667)
Another limitation to consider is hybrid applications where you have portions of the database located in the cloud, and part on premises. If the federated part of the data exists in both places, then you will have to maintain two versions of the application code, since Federations is not implemented on premises.
##### SQL Federations #####
-For an overview of SQL Azure Federations, see [Federations in SQL Azure]( http://go.microsoft.com/fwlink/?LinkId=252668).
+For an overview of SQL Database Federations, see [Federations in SQL Database]( http://go.microsoft.com/fwlink/?LinkId=252668).
Federating for scalability requires some modifications to your already well-designed database schema. There are two major issues:
@@ -122,7 +122,7 @@ In order to decide what to federate on, you need to examine your database schema
For example, in the well-known AdventureWorks sample database, one possible aggregate is the set {Customer, Order, OrderLine, and possibly a few more}. Another possible aggregate is {Supplier, Product, OrderLine, Order}.
-Each aggregate is a candidate for federating. You must evaluate where you expect growth in size, and also examine your application’s work load: queries that “align well” with the federating scheme, i.e. which don’t require data from more than one federation member, will run well. Those that don’t align well will require logic in the application layer, because SQL Azure does not currently support cross-database joins.
+Each aggregate is a candidate for federating. You must evaluate where you expect growth in size, and also examine your application’s work load: queries that “align well” with the federating scheme, i.e. which don’t require data from more than one federation member, will run well. Those that don’t align well will require logic in the application layer, because SQL Database does not currently support cross-database joins.
To see an example of a design analysis that examines the AdventureWorks database in order to federate it, and shows you step-by-step the considerations involved in the design, see [Scale-First Approach to Database Design with Federations: Part 1 – Picking Federations and Picking the Federation Key](http://go.microsoft.com/fwlink/?LinkId=252671).
@@ -138,28 +138,28 @@ If your application uses a relational database, then good database design is alw
* [Stairway to Database Design](http://go.microsoft.com/fwlink/?LinkId=252676)
* [Database Design](http://go.microsoft.com/fwlink/?LinkId=252677)
-Use of SQL Azure Federations in a Windows Azure Cloud Service requires some modification of classic design principles. However, most things true of good design for an on-premises SQL Server database are a necessary starting point for converting to SQL Azure Federations. If you are considering changing an application that uses a SQL database over to use Federations, validate the existing schema design. Implementing Federations assumes that the original database is well-designed.
+Use of SQL Database Federations in a Windows Azure Cloud Service requires some modification of classic design principles. However, most things true of good design for an on-premises SQL Server database are a necessary starting point for converting to SQL Database Federations. If you are considering changing an application that uses a SQL database over to use Federations, validate the existing schema design. Implementing Federations assumes that the original database is well-designed.
##### Do-It-Yourself Partitioning #####
-There are a number of samples that show ways of partitioning data. If you decide not to use Federations to partition your SQL Azure database, you must choose a method of partitioning that is appropriate to your application. Here are some examples:
+There are a number of samples that show ways of partitioning data. If you decide not to use Federations to partition your SQL Database instance, you must choose a method of partitioning that is appropriate to your application. Here are some examples:
-* A comprehensive account written before the release of Federations is [How to Shard with SQL Azure](http://go.microsoft.com/fwlink/?LinkId=252678).
-* [SQL Server and SQL Azure Shard Library]( http://go.microsoft.com/fwlink/?LinkId=252679)
+* A comprehensive account written before the release of Federations is [How to Shard with SQL Database](http://go.microsoft.com/fwlink/?LinkId=252678).
+* [SQL Server and SQL Database Shard Library]( http://go.microsoft.com/fwlink/?LinkId=252679)
##### Partitioning Other Resources #####
-You can partition other resources besides SQL Azure. For example you might wish to partition application servers and dedicate them to specific databases. Let’s assume your application contained N app servers, and also N databases. If each app server is allowed to access each database, that will consume N squared database connections which in some cases may hit a hard Windows Azure limit. But if you restrict each app server to only a few databases, then you will significantly reduce the number of connections used.
+You can partition other resources besides SQL Database. For example you might wish to partition application servers and dedicate them to specific databases. Let’s assume your application contained N app servers, and also N databases. If each app server is allowed to access each database, that will consume N squared database connections which in some cases may hit a hard Windows Azure limit. But if you restrict each app server to only a few databases, then you will significantly reduce the number of connections used.
Depending on your application you may be able to apply similar reasoning to other resources.
#### Caching ####
-The Windows Azure Caching Service provides distributed elastic memory for caching things like ASP.net session state, or commonly referenced values from SQL Azure reference tables. Because the objects are in distributed memory, there is a considerable performance gain possible. Because Windows Azure handles the caching infrastructure, there is little development cost in implementing it.
+The Windows Azure Caching Service provides distributed elastic memory for caching things like ASP.net session state, or commonly referenced values from SQL Database reference tables. Because the objects are in distributed memory, there is a considerable performance gain possible. Because Windows Azure handles the caching infrastructure, there is little development cost in implementing it.
-Plan to provide enough caching capacity so that you can cache frequently accessed objects. In SQL Azure there are frequently reference tables used to convert numeric codes into longer descriptive character strings. These tables often include data such as Country and City names, valid Postal Code values, names of Departments within your company, etc. For smaller tables it may make sense to store the entire table in cache, for others you might only store the most frequently used values. The performance gain comes in multi-join queries that involve this data: for each value that is found in the cache, several disk accesses are saved. A good introduction and discussion of performance and caching in Windows Azure is [Introducing the Windows Azure Caching Service (http://go.microsoft.com/fwlink/?LinkId=252680)](http://go.microsoft.com/fwlink/?LinkId=252680). A more recent blog post on the subject is at [Windows #Azure Caching Performance Considerations (http://go.microsoft.com/fwlink/?LinkId=252681)](http://go.microsoft.com/fwlink/?LinkId=252681).
+Plan to provide enough caching capacity so that you can cache frequently accessed objects. In SQL Database there are frequently reference tables used to convert numeric codes into longer descriptive character strings. These tables often include data such as Country and City names, valid Postal Code values, names of Departments within your company, etc. For smaller tables it may make sense to store the entire table in cache, for others you might only store the most frequently used values. The performance gain comes in multi-join queries that involve this data: for each value that is found in the cache, several disk accesses are saved. A good introduction and discussion of performance and caching in Windows Azure is [Introducing the Windows Azure Caching Service (http://go.microsoft.com/fwlink/?LinkId=252680)](http://go.microsoft.com/fwlink/?LinkId=252680). A more recent blog post on the subject is at [Windows #Azure Caching Performance Considerations (http://go.microsoft.com/fwlink/?LinkId=252681)](http://go.microsoft.com/fwlink/?LinkId=252681).
#### Scenario: Using Queuing in Windows Azure Applications ####
@@ -261,7 +261,7 @@ Windows Azure is designed to run multiple concurrent applications, replicated fo
* Physical location of services
-These considerations apply to all application architectures, because they are determined by the physical infrastructure of Windows Azure data centers. For detailed discussion, see the [SQL Azure Performance and Elasticity Guide](http://go.microsoft.com/fwlink/?LinkID=252666).
+These considerations apply to all application architectures, because they are determined by the physical infrastructure of Windows Azure data centers. For detailed discussion, see the [SQL Database Performance and Elasticity Guide](http://go.microsoft.com/fwlink/?LinkID=252666).
### Network latency ###
@@ -273,11 +273,11 @@ Take into account that there probably will be more, since the cloud data center
If possible, co-locate different nodes or application layers within the same data center. Otherwise network latency and cost will be greater.
-For example, locate the web application in the same data center as the SQL Azure database that it accesses, rather than in a different data center, or on-premises.
+For example, locate the web application in the same data center as the SQL Database instance that it accesses, rather than in a different data center, or on-premises.
### Transient connections ###
-Your application MUST be able to handle dropped connections. Dropped connections are inevitable and intrinsic to the cloud architecture (e.g. ops like replacing a dead node, splitting a Federation member in SQL Azure, etc). The best framework for doing this right now is [The Transient Fault Handling Application Block](http://go.microsoft.com/fwlink/?LinkID=236901).
+Your application MUST be able to handle dropped connections. Dropped connections are inevitable and intrinsic to the cloud architecture (e.g. ops like replacing a dead node, splitting a Federation member in SQL Database, etc). The best framework for doing this right now is [The Transient Fault Handling Application Block](http://go.microsoft.com/fwlink/?LinkID=236901).
### Throttling ###
@@ -325,16 +325,16 @@ Being able to trouble shoot performance problems at runtime requires up-front wo
There are tools available for monitoring the on-going performance of every Windows Azure service. In addition logging facilities should be built into applications that provide detailed information needed for trouble-shooting and resolving performance issues.
-### SQL Azure ###
+### SQL Database ###
Note that the SQL Profiler is not currently available in Windows Azure. There are several work-arounds to gain the needed performance information.One alternative during development is to do initial testing in an on-premises version of the database, where SQL Profiler is available.
-You can also use the SET STATISTICS Transact-SQL command, and use SQL Server Management Studio to view the execution plan generated by a query, since coding efficient queries is a key to performance. For a detailed discussion, and a step-by-step explanation of how to do this, see [Gaining Performance Insight into SQL Azure](http://go.microsoft.com/fwlink/?LinkId=252877). Another interesting approach is at Analyze performance between [SQL Azure and SQL Server on premise](http://go.microsoft.com/fwlink/?LinkId=252878).
+You can also use the SET STATISTICS Transact-SQL command, and use SQL Server Management Studio to view the execution plan generated by a query, since coding efficient queries is a key to performance. For a detailed discussion, and a step-by-step explanation of how to do this, see [Gaining Performance Insight into SQL Database](http://go.microsoft.com/fwlink/?LinkId=252877). Another interesting approach is at Analyze performance between [SQL Database and SQL Server on premise](http://go.microsoft.com/fwlink/?LinkId=252878).
Two topics about Dynamic Management Views are:
-* [Monitoring SQL Azure Using Dynamic Management Views](http://go.microsoft.com/fwlink/?LinkId=236195)
-* [Useful DMV’s for SQL Azure to analyze if you miss SQL Profiler](http://go.microsoft.com/fwlink/?LinkId=252879)
+* [Monitoring SQL Database Using Dynamic Management Views](http://go.microsoft.com/fwlink/?LinkId=236195)
+* [Useful DMV’s for SQL Database to analyze if you miss SQL Profiler](http://go.microsoft.com/fwlink/?LinkId=252879)
### Analysis Resources and Tools ###
@@ -342,12 +342,12 @@ A number of third-party non-Microsoft tools are available for analyzing Windows
- [Cerebrata](http://go.microsoft.com/fwlink/?LinkId=252880)
-- [SQL Server and SQL Azure Performance Testing: Enzo SQL Baseline](http://enzosqlbaseline.codeplex.com/)
+- [SQL Server and SQL Database Performance Testing: Enzo SQL Baseline](http://enzosqlbaseline.codeplex.com/)
Other Resources
-* [SQL Azure Performance and Elasticity Guide](http://go.microsoft.com/fwlink/?LinkID=252666)
-* [SQL Azure](http://go.microsoft.com/fwlink/?LinkId=246930)
+* [SQL Database Performance and Elasticity Guide](http://go.microsoft.com/fwlink/?LinkID=252666)
+* [SQL Database](http://go.microsoft.com/fwlink/?LinkId=246930)
* [Storage](http://go.microsoft.com/fwlink/?LinkId=246933)
* [Networking]( http://go.microsoft.com/fwlink/?LinkId=252882)
* [Service Bus]( http://go.microsoft.com/fwlink/?LinkId=246934)
View
82 Shared/Chunks/tshootguide.md
@@ -58,9 +58,9 @@ describe how to implement them.
[Windows Azure Virtual Machines](Vms)
-[Windows Azure Platform Services](PlatformServices)
+[Windows Azure Services](PlatformServices)
-[SQL Azure Troubleshooting](SQLTroubleshooting)
+[SQL Database Troubleshooting](SQLTroubleshooting)
<h2 id="BestPractices">Best Practices for Troubleshooting in Windows Azure</h2>
@@ -96,7 +96,7 @@ network connections inherent in shared resources on the internet. Some
examples are:
- Shared computer resources such as Windows Azure Cloud Services and
- SQL Azure (to give two examples) can be slightly less or more
+ SQL Database (to give two examples) can be slightly less or more
responsive from moment to moment.
- Responsiveness delays due to providing durability for services. For example, SQL
Azure keeps multiple copies of databases consistent in order to
@@ -122,7 +122,7 @@ Microsoft Enterprise Library is a collection of reusable application
blocks that address common cross-cutting concerns in enterprise software
development. The Microsoft Enterprise Library Integration Pack for
Windows Azure is an extension to Microsoft Enterprise Library 5.0 that
-can be used with the Windows Azure technology platform. It includes the
+can be used with Windows Azure. It includes the
Autoscaling Application Block, Transient Fault Handling Application
Block, blob configuration source, protected configuration provider, and
learning materials. Another, simpler .NET library with fewer features is the
@@ -234,8 +234,8 @@ diagnostics data collected by applications running in Windows Azure. See
Cloud Storage Studio 2 is a Windows (WPF) based client for managing
Windows Azure Storage.
-Azure Management Cmdlets is a set of PowerShell Cmdlets for managing
-Windows Azure Storage, Hosted Services, SQL Azure databases and
+Azure Management Cmdlets is a set of Windows PowerShell cmdlets for managing
+Windows Azure Storage, Hosted Services, SQL Database instances, and
Diagnostics. It also provides cmdlets to back up and restore storage
accounts.
@@ -291,7 +291,7 @@ do rudimentary tests without having to deploying your application. The
debugging tools you use vary depending upon the programming language and the development tools
you are using.
-After an application has been deployed, you can debug in the cloud using a debugger like Visual Studio. The requires creating a debug build and deploying it. In order to do this,you must connect to a specific role instance. If you have a complex application with multiple roles and role instances, it can be very difficult to determine to which role instance to connect. Visual Studio 2010 Ultimate supports IntelliTrace, which allows .NET roles to track debug information. When a problem occurs you can download this information and load it into Visual Studio. You can look at each role instance's IntelliTrace log to determine where the problem occured. While there are some drawbacks to debugging in the cloud, there are some circumstancesin which it is required. Not all Azure Platform Services have an emulator (for example Service Bus) and not all supported development tools (for example Mac and Linux) come with emulators.
+After an application has been deployed, you can debug in the cloud using a debugger like Visual Studio. The requires creating a debug build and deploying it. In order to do this,you must connect to a specific role instance. If you have a complex application with multiple roles and role instances, it can be very difficult to determine to which role instance to connect. Visual Studio 2010 Ultimate supports IntelliTrace, which allows .NET roles to track debug information. When a problem occurs you can download this information and load it into Visual Studio. You can look at each role instance's IntelliTrace log to determine where the problem occured. While there are some drawbacks to debugging in the cloud, there are some circumstancesin which it is required. Not all Windows Azure Services have an emulator (for example Service Bus) and not all supported development tools (for example Mac and Linux) come with emulators.
**Once you have debugged your application locally you will most likely
have to rely on the instrumentation built into your application to
@@ -301,8 +301,8 @@ determine where problems are occurring. **
For debugging Node.JS applications, you can use the Node-Inspector tool
which is available on [GitHub](https://github.com/dannycoates/node-inspector). Node-Inspector can be run locally on your
-development machine using the Azure storage emulator. For more
-information see Jim Wang’s blog: [Debugging Node in the Azure Emulator].
+development machine using the Windows Azure storage emulator. For more
+information see Jim Wang’s blog: [Debugging Node in the Windows Azure Emulator].
If you are debugging your application on Azure, install the full version
of IISNode from [GitHub](https://github.com/windowsazure/iisnode/downloads) on your web role, worker role, or VM instance. As
@@ -431,8 +431,8 @@ ways:
- Diagnostic storage incurs a monthly cost when stored in Windows
Azure storage.
-Cost is of particular importance because one of the key benefits of the
-Windows Azure platform is cost reduction. The only way to eliminate the
+Cost is of particular importance because one of the key benefits of
+Windows Azure is cost reduction. The only way to eliminate the
cost of using WAD today is to leave the data on the virtual machine.
This may work in a small deployment, but is impractical where there are
many instances. Here are a few ways to minimize the financial impact:
@@ -476,7 +476,7 @@ demonstrated include:
- Windows Azure SDK
- Windows Azure Storage Analytics
- Windows Azure Diagnostics
-- SQL Azure REST API
+- SQL Database REST API
- Windows Azure Traffic Manager REST API
- Windows PowerShell
@@ -504,9 +504,9 @@ with the operating systems and platforms in use. For example:
start with the product documentation, see [https://help.ubuntu.com/].
- CentOS 6.2 Linux. For more information, see [http://centos.org/].
-<h2 id="PlatformServices">Troubleshooting Windows Azure Platform Services</h2>
+<h2 id="PlatformServices">Troubleshooting Windows Azure Services</h2>
-Many of the Windows Azure Services such as Windows Azure SQL Database, Windows Azure
+Many of the Windows Azure services such as Windows Azure SQL Database, Windows Azure
Active Directory, and Windows Azure storage have troubleshooting advice
that is specific to their use, regardless whether the application is
executing on Windows Azure, what programming language or libraries it was built
@@ -663,8 +663,8 @@ means an exhaustive list. The key to writing supportable Windows Azure SQL Datab
is to examine the return codes and make sure that you have solid retry
code to handle failures.
-Your application must handle login failures gracefully. SQL Azure
-Databases require the use of SQL Authentication. If you cannot
+Your application must handle login failures gracefully. SQL Database
+instances require the use of SQL Authentication. If you cannot
successfully log in, either your credentials are not valid or the
database you requested is not available.
@@ -674,9 +674,9 @@ available (you can check this using the [Azure Health Status] page), the
likely cause is configuration issues in your on-site installation. For
instance, you may be unable to resolve the name (which can be tested
with tools such as tracert), you may have a firewall blocking port 1433
-that is used by SQL Azure, or you may be using a proxy server that is
+that is used by SQL Database, or you may be using a proxy server that is
not configured properly. Use the same techniques to troubleshoot these
-difficulties that you would for SQL Server. For more information, see [SQL Azure Connectivity Troubleshooting Guide] and [Troubleshooting SQL Azure].
+difficulties that you would for SQL Server. For more information, see [SQL Database Connectivity Troubleshooting Guide] and [Troubleshooting SQL Database].
Your application must handle general network errors. You may receive
general network errors because Windows Azure SQL Database might disconnect users
@@ -692,10 +692,10 @@ you would use with SQL Server. For more information, see the following
topics:
- [Troubleshooting Queries] in SQL Server Books Online
-- [Troubleshoot and Optimize Queries with SQL Azure]
-- [SQL Azure Performance Considerations and Troubleshooting]
+- [Troubleshoot and Optimize Queries with SQL Database]
+- [SQL Database Performance Considerations and Troubleshooting]
- [Improving Your I/O Performance]
-- [System Center Monitoring Pack for SQL Azure]
+- [System Center Monitoring Pack for SQL Database]
Windows Azure SQL Database uses a subset of SQL Server error messages. For more
information about SQL Server errors, see [Errors and Events Reference
@@ -704,9 +704,9 @@ information about SQL Server errors, see [Errors and Events Reference
If you need to recover login names or passwords, contact your service
administrator, who can grant you proper access to the server and
database. Service administrators can also reset their own passwords
-using the Windows Azure Platform Management Portal.
+using the Windows Azure Management Portal.
-SQL Azure queries can fail for various reasons – a malformed query,
+SQL Database queries can fail for various reasons – a malformed query,
network issues, and so on. Some errors are transient, meaning the
problem often goes away by itself. For this subset of errors, it makes
sense to retry the query after a short interval. If the query still
@@ -716,13 +716,13 @@ away no matter how many times you submit the same query. In short,
implementing robust retry logic requires some thought. A tabular data
stream (TDS) error token is sent prior to disconnecting users, when
possible. To improve application experience, we recommend that you
-implement the retry logic in your SQL Azure applications to catch these
+implement the retry logic in your SQL Database applications to catch these
errors. When an error occurs, re-establish the connection, and then
re-execute the failed commands or the query. For more information, see
the following links:
-- [Retry Logic for Transient Failures in SQL Azure]
-- [SQL Azure Retry Logic Sample]
+- [Retry Logic for Transient Failures in SQL Database]
+- [SQL Database Retry Logic Sample]
- [The Transient Fault Handling Application Block]
###Windows Azure SQL Backup and Restore Strategy
@@ -732,31 +732,31 @@ environment and tools available. In many ways the risks have been
mediated by the database being in the Microsoft data centers. The tools
that we have today cover the other risk factors, however better tools
are coming to make the job much easier. Red-gate recently published a
-free tool for SQL Azure backup and restore which can be found here: [http://www.red-gate.com/products/dba/sql-azure-backup/].
+free tool for SQL Database backup and restore which can be found here: [http://www.red-gate.com/products/dba/sql-azure-backup/].
-SQL Azure Data Sync enables you to easily create and schedule
+SQL Database Data Sync enables you to easily create and schedule
bi-directional synchronizations from within the Data Sync web site
without the need to write a single line of code. You can find more
information here:
http://msdn.microsoft.com/en-us/library/windowsazure/hh456371.aspx.
-For more information on SQL Azure backup and Restore strategies see the
+For more information on SQL Database backup and Restore strategies see the
following articles:
-- This topic gives an overview of SQL Azure Backup and Restore
+- This topic gives an overview of SQL Database Backup and Restore
Strategies:
[http://social.technet.microsoft.com/wiki/contents/articles/1792.sql-azure-backup-and-restore-strategy.aspx]
- This topic explains how to back up a database to another database on
the same server:
[http://msdn.microsoft.com/en-us/library/windowsazure/ff951631.aspx]
-- This topic explains how to export an existing SQL Azure database to
+- This topic explains how to export an existing SQL Database instance to
a blob on a given storage account:
[http://msdn.microsoft.com/en-us/library/windowsazure/hh335292.aspx]
-- This topic explains how to import an existing SQL Azure database
+- This topic explains how to import an existing SQL Database instance
from a bacpac file stored in a blob:
[http://msdn.microsoft.com/en-us/library/windowsazure/hh335291.aspx]
- This topic describes the business continuity capabilities provided
- by SQL Azure:
+ by SQL Database:
[http://msdn.microsoft.com/en-us/library/windowsazure/hh852669.aspx]
<h2 id="Cache">Windows Azure Cache Services</h2>
@@ -807,7 +807,7 @@ For more information on quota-related errors, see [Understanding Quotas] and [Tr
[AVIcode]: http://www.microsoft.com/en-us/server-cloud/system-center/avicode.aspx
[profile]: http://msdn.microsoft.com/en-us/library/windowsazure/hh369930.aspx
[VM Assitant]: http://azurevmassist.codeplex.com/
-[Debugging Node in the Azure Emulator]: http://weblogs.asp.net/jimwang/archive/2012/04/17/debugging-node-node-inspector-in-the-azure-emulator.aspx
+[Debugging Node in the Windows Azure Emulator]: http://weblogs.asp.net/jimwang/archive/2012/04/17/debugging-node-node-inspector-in-the-azure-emulator.aspx
[Debugging with Node-Inspector]: http://howtonode.org/debugging-with-node-inspector
[IntelliTrace]: http://msdn.microsoft.com/en-us/library/dd264915.aspx
[IntelliTrace to debug Windows Azure Cloud Services]: http://blogs.msdn.com/b/jnak/archive/2010/06/07/using-intellitrace-to-debug-windows-azure-cloud-services.aspx
@@ -836,16 +836,16 @@ For more information on quota-related errors, see [Understanding Quotas] and [Tr
[Best Practices for Leveraging Windows Azure Service Bus Brokered Messaging API]: http://windowsazurecat.com/2011/09/best-practices-leveraging-windows-azure-service-bus-brokered-messaging-api/
[Troubleshooting the Service Bus]: http://msdn.microsoft.com/en-us/library/windowsazure/ee706702.aspx
[Azure Health Status]: http://go.microsoft.com/fwlink/p/?LinkId=168847
-[SQL Azure Connectivity Troubleshooting Guide]: http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-connectivity-troubleshooting-guide.aspx
-[Troubleshooting SQL Azure]: http://msdn.microsoft.com/en-us/library/ee730906.aspx
+[SQL Database Connectivity Troubleshooting Guide]: http://social.technet.microsoft.com/wiki/contents/articles/sql-azure-connectivity-troubleshooting-guide.aspx
+[Troubleshooting SQL Database]: http://msdn.microsoft.com/en-us/library/ee730906.aspx
[Troubleshooting Queries]: http://go.microsoft.com/fwlink/p/?LinkId=166623
-[Troubleshoot and Optimize Queries with SQL Azure]: http://social.technet.microsoft.com/wiki/contents/articles/1104.troubleshoot-and-optimize-queries-with-sql-azure.aspx
-[SQL Azure Performance Considerations and Troubleshooting]: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DBI314
+[Troubleshoot and Optimize Queries with SQL Database]: http://social.technet.microsoft.com/wiki/contents/articles/1104.troubleshoot-and-optimize-queries-with-sql-azure.aspx
+[SQL Database Performance Considerations and Troubleshooting]: http://channel9.msdn.com/Events/TechEd/NorthAmerica/2011/DBI314
[Improving Your I/O Performance]: http://blogs.msdn.com/b/sqlazure/archive/2010/07/27/10043069.aspx?PageIndex=2#comments
-[System Center Monitoring Pack for SQL Azure]: http://www.microsoft.com/download/en/details.aspx?id=28951
+[System Center Monitoring Pack for SQL Database]: http://www.microsoft.com/download/en/details.aspx?id=28951
[Errors and Events Reference (Database Engine)]: http://go.microsoft.com/fwlink/p/?LinkId=166622
-[Retry Logic for Transient Failures in SQL Azure]: http://social.technet.microsoft.com/wiki/contents/articles/4235.retry-logic-for-transient-failures-in-sql-azure.aspx
-[SQL Azure Retry Logic Sample]: http://code.msdn.microsoft.com/windowsazure/SQL-Azure-Retry-Logic-2d0a8401
+[Retry Logic for Transient Failures in SQL Database]: http://social.technet.microsoft.com/wiki/contents/articles/4235.retry-logic-for-transient-failures-in-sql-azure.aspx
+[SQL Database Retry Logic Sample]: http://code.msdn.microsoft.com/windowsazure/SQL-Azure-Retry-Logic-2d0a8401
[The Transient Fault Handling Application Block]: http://msdn.microsoft.com/en-us/library/hh680934(PandP.50).aspx
[Microsoft Enterprise Library 5.0 Integration Pack for Windows Azure]: http://msdn.microsoft.com/en-us/library/hh680918%28v=pandp.50%29.aspx
[Take Control of Logging and Tracing in Windows Azure]: http://msdn.microsoft.com/en-us/magazine/ff714589.aspx
View
18 Shared/Chunks/website-from-gallery.md
@@ -1,9 +1,9 @@
-The Azure Gallery makes available a wide range of popular web applications developed by Microsoft, third party companies and open source software initiatives. Web applications created from the Azure Gallery do not require installation of any software other than the browser used to connect to the Windows Azure portal. When creating websites from the Azure Gallery you should be able to create, deploy, and have a fully operational website running in 3 to 5 minutes.
+The Web Sites gallery makes available a wide range of popular web applications developed by Microsoft, third party companies and open source software initiatives. Web applications created from the gallery do not require installation of any software other than the browser used to connect to the Windows Azure portal. When creating web sites from the gallery you should be able to create, deploy, and have a fully operational web site running in 3 to 5 minutes.
-This topic describes how to create and publish a WordPress blog website from the Azure Gallery to a website.
+This topic describes how to create and publish a WordPress blog web site from the gallery to a web site.
-###Create and Publish a Website from the Azure Gallery to Windows Azure###
-Follow these steps to create, deploy and run a WordPress blog website on Windows Azure:
+###Create and publish a web site from the gallery to Windows Azure###
+Follow these steps to create, deploy and run a WordPress blog web site on Windows Azure:
1. Login to the Windows Azure portal.
2. Click the **Create New** icon on the bottom left of the Windows Azure portal.
@@ -11,8 +11,8 @@ Follow these steps to create, deploy and run a WordPress blog website on Windows
4. On the Configure Your App/Site Settings page enter or select appropriate values for all fields and click **Next**.
**Note**
- When choosing a region, select the region that is closest to your target audience. Selecting the region that is closest to the geographical location of your target audience will minimize latency for their connections to your website. If you have not determined the geographical location of your target audience then consider selecting a region in the central U.S. so that latency will be similar for users on both the east and west coasts.
-5. On the **Configure Your App/Database Settings** page select **New Database**, enter appropriate values for all fields and then click **Complete**. After you click **Complete** Windows Azure will initiate build and deploy operations. While the website is being built and deployed the status of these operations is displayed at the bottom of the Web Sites page. After all operations are performed a final status message indicates whether the operations succeeded. When this message indicates that operations were successful click **Ok**.
-6. Open the website's **Dashboard** management page.
-7. On the **Dashboard** management page click the link under **Site Url** to open the site’s welcome page. Enter appropriate configuration information required by WordPress and click **Install Wordpress** to finalize configuration and open the website’s login page.
-8. Login to the new WordPress website by entering the username and password that you specified on the **Welcome** page.
+ When choosing a region, select the region that is closest to your target audience. Selecting the region that is closest to the geographical location of your target audience will minimize latency for their connections to your web site. If you have not determined the geographical location of your target audience then consider selecting a region in the central U.S. so that latency will be similar for users on both the east and west coasts.
+5. On the **Configure Your App/Database Settings** page select **New Database**, enter appropriate values for all fields and then click **Complete**. After you click **Complete** Windows Azure will initiate build and deploy operations. While the web site is being built and deployed the status of these operations is displayed at the bottom of the Web Sites page. After all operations are performed a final status message indicates whether the operations succeeded. When this message indicates that operations were successful click **Ok**.
+6. Open the web site's **Dashboard** management page.
+7. On the **Dashboard** management page click the link under **Site Url** to open the site’s welcome page. Enter appropriate configuration information required by WordPress and click **Install Wordpress** to finalize configuration and open the web site’s login page.
+8. Login to the new WordPress web site by entering the username and password that you specified on the **Welcome** page.
Please sign in to comment.
Something went wrong with that request. Please try again.