Skip to content

Commit

Permalink
Markdig conversion test (MicrosoftDocs#467)
Browse files Browse the repository at this point in the history
markdig migration
  • Loading branch information
bennage authored and Mike Wasson committed Apr 6, 2018
1 parent 4ec95a9 commit e67b751
Show file tree
Hide file tree
Showing 53 changed files with 696 additions and 666 deletions.
1 change: 0 additions & 1 deletion docs/antipatterns/extraneous-fetching/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -229,7 +229,6 @@ Here is the corresponding telemetry for the `AggregateOnDatabaseAsync` method. T


[BusyDatabase]: ../busy-database/index.md
[chatty-io]: ../chatty-io.md
[data-partitioning]: ../../best-practices/data-partitioning.md
[new-relic]: https://newrelic.com/application-monitoring

Expand Down
276 changes: 134 additions & 142 deletions docs/aws-professional/services.md

Large diffs are not rendered by default.

3 changes: 1 addition & 2 deletions docs/best-practices/retry-service-specific.md
Original file line number Diff line number Diff line change
Expand Up @@ -474,7 +474,6 @@ public async static Task<SqlDataReader> ExecuteReaderWithRetryAsync(this SqlComm

}, cancellationToken);
}

```

This asynchronous extension method can be used as follows.
Expand Down Expand Up @@ -788,7 +787,7 @@ namespace RetryCodeSamples
try
{
var retryTimeInMilliseconds = TimeSpan.FromSeconds(4).Milliseconds; // delay between retries
// Using object-based configuration.
var options = new ConfigurationOptions
{
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -291,7 +291,6 @@ Now let's take a look at our template. Our first resource named `NSG1` deploys t
],
"outputs": {}
}

```

Let's take a closer look at how we specify our property values in the `securityRules` child resource. All of our properties are referenced using the `parameter()` function, and then we use the dot operator to reference our `securityRules` array, indexed by the current value of the iteration. Finally, we use another dot operator to reference the name of the object.
Expand All @@ -300,18 +299,18 @@ Let's take a closer look at how we specify our property values in the `securityR

If you would like to experiment with this template, follow these steps:

1. Go to the Azure portal, select the **+** icon, and search for the **template deployment** resource type, and select it.
2. Navigate to the **template deployment** page, select the **create** button. This button opens the **custom deployment** blade.
3. Select the **edit template** button.
4. Delete the empty template.
5. Copy and paste the sample template into the right pane.
6. Select the **save** button.
7. When you are returned to the **custom deployment** pane, select the **edit parameters** button.
1. Go to the Azure portal, select the **+** icon, and search for the **template deployment** resource type, and select it.
2. Navigate to the **template deployment** page, select the **create** button. This button opens the **custom deployment** blade.
3. Select the **edit template** button.
4. Delete the empty template.
5. Copy and paste the sample template into the right pane.
6. Select the **save** button.
7. When you are returned to the **custom deployment** pane, select the **edit parameters** button.
8. On the **edit parameters** blade, delete the existing template.
9. Copy and paste the sample parameter template from above.
10. Select the **save** button, which returns you to the **custom deployment** blade.
11. On the **custom deployment** blade, select your subscription, either create new or use existing resource group, and select a location. Review the terms and conditions, and select the **I agree** checkbox.
12. Select the **purchase** button.
12. Select the **purchase** button.

## Next steps

Expand Down
2 changes: 1 addition & 1 deletion docs/checklist/dev-ops.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ Shared documentation is critical. Encourage team members to contribute and share

**Follow least-privilege principles when granting access to resources.** Carefully manage access to resources. Access should be denied by default, unless a user is explicitly given access to a resource. Only grant a user access to what they need to complete their tasks. Track user permissions and perform regular security audits.

**Use role-based access control.** Assigning user accounts and access to resources should not be a manual process. Use [Role-Based Access Control][rbac] (RBAC) grant access based on [Azure Active Directory][azure-ad] identities and groups.
<strong>Use role-based access control.</strong> Assigning user accounts and access to resources should not be a manual process. Use [Role-Based Access Control][rbac] (RBAC) grant access based on [Azure Active Directory][azure-ad] identities and groups.

**Use a bug tracking system to track issues.** Without a good way to track issues, it's easy to miss items, duplicate work, or introduce additional problems. Don't rely on informal person-to-person communication to track the status of bugs. Use a bug tracking tool to record details about problems, assign resources to address them, and provide an audit trail of progress and status.

Expand Down
18 changes: 9 additions & 9 deletions docs/data-guide/relational-data/data-warehousing.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,15 +145,15 @@ The following tables summarize the key differences in capabilities.

### Security capabilities

| | Azure SQL Database | SQL Server in a virtual machine | SQL Data Warehouse | Apache Hive on HDInsight | Hive LLAP on HDInsight |
| --- | --- | --- | --- | --- | --- | -- |
| Authentication | SQL / Azure Active Directory (Azure AD) | SQL / Azure AD / Active Directory | SQL / Azure AD | local / Azure AD <sup>1</sup> | local / Azure AD <sup>1</sup> |
| Authorization | Yes | Yes | Yes | Yes | Yes <sup>1</sup> | Yes <sup>1</sup> |
| Auditing | Yes | Yes | Yes | Yes | Yes <sup>1</sup> | Yes <sup>1</sup> |
| Data encryption at rest | Yes <sup>2</sup> | Yes <sup>2</sup> | Yes <sup>2</sup> | Yes <sup>2</sup> | Yes <sup>1</sup> | Yes <sup>1</sup> |
| Row-level security | Yes | Yes | Yes | No | Yes <sup>1</sup> | Yes <sup>1</sup> |
| Supports firewalls | Yes | Yes | Yes | Yes | Yes <sup>3</sup> | Yes <sup>3</sup> |
| Dynamic data masking | Yes | Yes | Yes | No | Yes <sup>1</sup> | Yes <sup>1</sup> |
| | Azure SQL Database | SQL Server in a virtual machine | SQL Data Warehouse | Apache Hive on HDInsight | Hive LLAP on HDInsight |
|-------------------------|-----------------------------------------|-----------------------------------|--------------------|-------------------------------|-------------------------------|
| Authentication | SQL / Azure Active Directory (Azure AD) | SQL / Azure AD / Active Directory | SQL / Azure AD | local / Azure AD <sup>1</sup> | local / Azure AD <sup>1</sup> |
| Authorization | Yes | Yes | Yes | Yes | Yes <sup>1</sup> |
| Auditing | Yes | Yes | Yes | Yes | Yes <sup>1</sup> |
| Data encryption at rest | Yes <sup>2</sup> | Yes <sup>2</sup> | Yes <sup>2</sup> | Yes <sup>2</sup> | Yes <sup>1</sup> |
| Row-level security | Yes | Yes | Yes | No | Yes <sup>1</sup> |
| Supports firewalls | Yes | Yes | Yes | Yes | Yes <sup>3</sup> |
| Dynamic data masking | Yes | Yes | Yes | No | Yes <sup>1</sup> |

[1] Requires using a [domain-joined HDInsight cluster](/azure/hdinsight/domain-joined/apache-domain-joined-introduction).

Expand Down
11 changes: 6 additions & 5 deletions docs/data-guide/relational-data/online-analytical-processing.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,8 +136,9 @@ The following tables summarize the key differences in capabilities.

### Scalability Capabilities

| | Azure Analysis Services | SQL Server Analysis Services | SQL Server with Columnstore Indexes | Azure SQL Database with Columnstore Indexes |
| --- | --- | --- | --- | --- |
| Redundant regional servers for high availability | Yes | No | Yes | Yes |
| Supports query scale out | Yes | No | Yes | No |
| Dynamic scalability (scale up) | Yes | No | Yes | No |
| | Azure Analysis Services | SQL Server Analysis Services | SQL Server with Columnstore Indexes | Azure SQL Database with Columnstore Indexes |
|--------------------------------------------------|-------------------------|------------------------------|-------------------------------------|---------------------------------------------|
| Redundant regional servers for high availability | Yes | No | Yes | Yes |
| Supports query scale out | Yes | No | Yes | No |
| Dynamic scalability (scale up) | Yes | No | Yes | No |

39 changes: 22 additions & 17 deletions docs/data-guide/relational-data/online-transaction-processing.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,15 +90,17 @@ To narrow the choices, start by answering these questions:
The following tables summarize the key differences in capabilities.

### General capabilities
| | Azure SQL Database | SQL Server in an Azure virtual machine | Azure Database for MySQL | Azure Database for PostgreSQL |
| --- | --- | --- | --- | --- | --- |
| Is Managed Service | Yes | No | Yes | Yes |
| Runs on Platform | N/A | Windows, Linux, Docker | N/A | N/A |
| Programmability <sup>1</sup> | T-SQL, .NET, R | T-SQL, .NET, R, Python | T-SQL, .NET, R, Python | SQL | SQL |

| | Azure SQL Database | SQL Server in an Azure virtual machine | Azure Database for MySQL | Azure Database for PostgreSQL |
|------------------------------|--------------------|----------------------------------------|--------------------------|-------------------------------|
| Is Managed Service | Yes | No | Yes | Yes |
| Runs on Platform | N/A | Windows, Linux, Docker | N/A | N/A |
| Programmability <sup>1</sup> | T-SQL, .NET, R | T-SQL, .NET, R, Python | T-SQL, .NET, R, Python | SQL |

[1] Not including client driver support, which allows many programming languages to connect to and use the OLTP data store.

### Scalability capabilities

| | Azure SQL Database | SQL Server in an Azure virtual machine| Azure Database for MySQL | Azure Database for PostgreSQL|
| --- | --- | --- | --- | --- | --- |
| Maximum database instance size | [4 TB](/azure/sql-database/sql-database-resource-limits) | 256 TB | [1 TB](/azure/mysql/concepts-limits) | [1 TB](/azure/postgresql/concepts-limits) |
Expand All @@ -107,6 +109,7 @@ The following tables summarize the key differences in capabilities.
| Dynamic scalability (scale up) | Yes | No | Yes | Yes |

### Analytic workload capabilities

| | Azure SQL Database | SQL Server in an Azure virtual machine| Azure Database for MySQL | Azure Database for PostgreSQL|
| --- | --- | --- | --- | --- | --- |
| Temporal tables | Yes | Yes | No | No |
Expand All @@ -115,6 +118,7 @@ The following tables summarize the key differences in capabilities.
| Adaptive query processing | Yes | Yes | No | No |

### Availability capabilities

| | Azure SQL Database | SQL Server in an Azure virtual machine| Azure Database for MySQL | Azure Database for PostgreSQL|
| --- | --- | --- | --- | --- | --- |
| Readable secondaries | Yes | Yes | No | No |
Expand All @@ -123,16 +127,17 @@ The following tables summarize the key differences in capabilities.
| Point-in-time restore | Yes | Yes | Yes | Yes |

### Security capabilities
| | Azure SQL Database | SQL Server in an Azure virtual machine| Azure Database for MySQL | Azure Database for PostgreSQL|
| --- | --- | --- | --- | --- | --- |
| Row level security | Yes | Yes | Yes | Yes |
| Data masking | Yes | Yes | No | No |
| Transparent data encryption | Yes | Yes | Yes | Yes |
| Restrict access to specific IP addresses | Yes | Yes | Yes | Yes |
| Restrict access to allow VNET access only | Yes | Yes | No | No |
| Azure Active Directory authentication | Yes | Yes | No | No |
| Active Directory authentication | No | Yes | No | No |
| Multi-factor authentication | Yes | Yes | No | No |
| Supports [Always Encrypted](/sql/relational-databases/security/encryption/always-encrypted-database-engine) | Yes | Yes | Yes | No | No |
| Private IP | No | Yes | Yes | No | No |

| | Azure SQL Database | SQL Server in an Azure virtual machine | Azure Database for MySQL | Azure Database for PostgreSQL |
|-------------------------------------------------------------------------------------------------------------|--------------------|----------------------------------------|--------------------------|-------------------------------|
| Row level security | Yes | Yes | Yes | Yes |
| Data masking | Yes | Yes | No | No |
| Transparent data encryption | Yes | Yes | Yes | Yes |
| Restrict access to specific IP addresses | Yes | Yes | Yes | Yes |
| Restrict access to allow VNET access only | Yes | Yes | No | No |
| Azure Active Directory authentication | Yes | Yes | No | No |
| Active Directory authentication | No | Yes | No | No |
| Multi-factor authentication | Yes | Yes | No | No |
| Supports [Always Encrypted](/sql/relational-databases/security/encryption/always-encrypted-database-engine) | Yes | Yes | Yes | No |
| Private IP | No | Yes | Yes | No |

12 changes: 6 additions & 6 deletions docs/data-guide/technology-choices/analytical-data-stores.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,12 +61,12 @@ The following tables summarize the key differences in capabilities.

### Scalability capabilities

| | SQL Database | SQL Data Warehouse | HBase/Phoenix on HDInsight | Hive LLAP on HDInsight | Azure Analysis Services | Cosmos DB |
| --- | --- | --- | --- | --- | --- | --- |
| Redundant regional servers for high availability | Yes | Yes | Yes | No | No | Yes | Yes |
| Supports query scale out | No | Yes | Yes | Yes | Yes | Yes |
| Dynamic scalability (scale up) | Yes | Yes | No | No | Yes | Yes |
| Supports in-memory caching of data | Yes | Yes | No | Yes | Yes | No |
| | SQL Database | SQL Data Warehouse | HBase/Phoenix on HDInsight | Hive LLAP on HDInsight | Azure Analysis Services | Cosmos DB |
|--------------------------------------------------|--------------|--------------------|----------------------------|------------------------|-------------------------|-----------|
| Redundant regional servers for high availability | Yes | Yes | Yes | No | No | Yes |
| Supports query scale out | No | Yes | Yes | Yes | Yes | Yes |
| Dynamic scalability (scale up) | Yes | Yes | No | No | Yes | Yes |
| Supports in-memory caching of data | Yes | Yes | No | Yes | Yes | No |

### Security capabilities

Expand Down
5 changes: 4 additions & 1 deletion docs/data-guide/technology-choices/batch-processing.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,22 +49,25 @@ The following tables summarize the key differences in capabilities.
| Pricing model | Per batch job | By cluster hour | By cluster hour | By cluster hour | By cluster hour |

[1] With manual configuration and scaling.

### Integration capabilities

| | Azure Data Lake Analytics | SQL Data Warehouse | HDInsight with Spark | HDInsight with Hive | HDInsight with Hive LLAP |
| --- | --- | --- | --- | --- | --- |
| Access from Azure Data Lake Store | Yes | Yes | Yes | Yes | Yes |
| Query from Azure Storage | Yes | Yes | Yes | Yes | Yes |
| Query from external relational stores | Yes | No | Yes | No | No |

### Scalability capabilities

| | Azure Data Lake Analytics | SQL Data Warehouse | HDInsight with Spark | HDInsight with Hive | HDInsight with Hive LLAP |
| --- | --- | --- | --- | --- | --- |
| Scale-out granularity | Per job | Per cluster | Per cluster | Per cluster | Per cluster |
| Fast scale out (less than 1 minute) | Yes | Yes | No | No | No |
| In-memory caching of data | No | Yes | Yes | No | Yes |

### Security capabilities

| | Azure Data Lake Analytics | SQL Data Warehouse | HDInsight with Spark | Apache Hive on HDInsight | Hive LLAP on HDInsight |
| --- | --- | --- | --- | --- | --- |
| Authentication | Azure Active Directory (Azure AD) | SQL / Azure AD | No | local / Azure AD <sup>1</sup> | local / Azure AD <sup>1</sup> |
Expand Down
Loading

0 comments on commit e67b751

Please sign in to comment.