Skip to content

Commit 4c08742

Browse files
committed
proof-azure-sql-project
1 parent 3613e8c commit 4c08742

6 files changed

+29
-29
lines changed

articles/azure-sql/database/develop-overview.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,18 +16,18 @@ ms.custom: sqldbrb=2
1616
This article walks through the basic considerations that a developer should be aware of when writing code to connect to Azure SQL Database. This article applies to Azure SQL Database, Azure SQL Managed Instance and Elastic pools.
1717

1818
> [!TIP]
19-
> Look at the getting started guides for [Azure SQL Database](quickstart-content-reference-guide.md) and [Azure SQL Managed Instances](../managed-instance/quickstart-content-reference-guide.md) if you need to setup your Azure SQL Database.
19+
> Look at the getting started guides for [Azure SQL Database](quickstart-content-reference-guide.md) and [Azure SQL Managed Instances](../managed-instance/quickstart-content-reference-guide.md) if you need to set up your Azure SQL database.
2020
>
2121
2222
## Language and platform
2323

24-
You can use various [programming languages and platforms](connect-query-content-reference-guide.md) to connect and query Azure SQL Database. You can find [sample applications](https://azure.microsoft.com/resources/samples/?service=sql-database&sort=0) that you can use to connect to the Azure SQL Database.
24+
You can use various [programming languages and platforms](connect-query-content-reference-guide.md) to connect and query Azure SQL Database. You can find [sample applications](https://azure.microsoft.com/resources/samples/?service=sql-database&sort=0) that you can use to connect to the Azure SQL database.
2525

2626
You can leverage open-source tools like [cheetah](https://github.com/wunderlist/cheetah), [sql-cli](https://www.npmjs.com/package/sql-cli), [VS Code](https://code.visualstudio.com/). Additionally, Azure SQL Database works with Microsoft tools like [Visual Studio](https://www.visualstudio.com/downloads/) and [SQL Server Management Studio](https://msdn.microsoft.com/library/ms174173.aspx). You can also use the Azure portal, PowerShell, and REST APIs help you gain additional productivity.
2727

2828
## Authentication
2929

30-
Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database supports both SQL Server and [Azure Active Directory (AAD) authentication](aad-authentication-overview.md) users and logins. AAD logins are available only in SQL Managed Instance.
30+
Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database supports both SQL Server and [Azure Active Directory authentication](aad-authentication-overview.md) users and logins. Azure Active Directory (Azure AD) logins are available only in SQL Managed Instance.
3131

3232
Learn more about [managing database access and login](logins-create-manage.md).
3333

@@ -41,9 +41,9 @@ Avoid long-running transactions because any infrastructure or connection failure
4141

4242
## Resiliency
4343

44-
Azure SQL Database is a cloud service where you might expect transient errors that happen in the underlying infrastructure or in the communication between cloud entities. Although Azure SQL Database is resilient on the transitive infrastructure failures, these failures might affect your connectivity. When a transient error occurs while connecting to SQL Database, your code should [retry the call](troubleshoot-common-connectivity-issues.md). We recommend that retry logic use backoff logic, so that it does not overwhelm the SQL Database with multiple clients retrying simultaneously. Retry logic depends on the [error messages for SQL Database client programs](troubleshoot-common-errors-issues.md).
44+
Azure SQL Database is a cloud service where you might expect transient errors that happen in the underlying infrastructure or in the communication between cloud entities. Although Azure SQL Database is resilient on the transitive infrastructure failures, these failures might affect your connectivity. When a transient error occurs while connecting to SQL Database, your code should [retry the call](troubleshoot-common-connectivity-issues.md). We recommend that retry logic use backoff logic, so that it does not overwhelm the SQL database with multiple clients retrying simultaneously. Retry logic depends on the [error messages for SQL Database client programs](troubleshoot-common-errors-issues.md).
4545

46-
For more information about how to prepare for planned maintenance events on your Azure SQL Database, see [planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md).
46+
For more information about how to prepare for planned maintenance events on your Azure SQL database, see [planning for Azure maintenance events in Azure SQL Database](planned-maintenance.md).
4747

4848
## Network considerations
4949

articles/azure-sql/database/disaster-recovery-guidance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: sashan
1212
ms.reviewer: mathoma, carlrab
1313
ms.date: 06/21/2019
1414
---
15-
# Restore an Azure SQL Database or failover to a secondary
15+
# Restore an Azure SQL database or failover to a secondary
1616
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
1717

1818
Azure SQL Database offers the following capabilities for recovering from an outage:
@@ -88,7 +88,7 @@ Because your recovered database resides in a different server, you need to updat
8888

8989
For more information about changing connection strings, see the appropriate development language for your [connection library](connect-query-content-reference-guide.md#libraries).
9090

91-
### Configure Firewall Rules
91+
### Configure firewall rules
9292

9393
You need to make sure that the firewall rules configured on server and on the database match those that were configured on the primary server and primary database. For more information, see [How to: Configure Firewall Settings (Azure SQL Database)](firewall-configure.md).
9494

articles/azure-sql/database/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.custom: sqldbrb=1
1616

1717
For many people, SQLite provides their first experience of databases and SQL programming. It's inclusion in many operating systems and popular applications makes SQLite one the most widely deployed and used database engines in the world. And because it is likely the first database engine many people use, it can often end up as a central part of projects or applications. In such cases where the project or application outgrows the initial SQLite implementation, developers may need to migrate their data to a reliable, centralized data store.
1818

19-
Azure SQL Database serverless is a compute tier for single databases that automatically scales compute based on workload demand, and bills for the amount of compute used per second. The serverless compute tier also automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns.
19+
Azure SQL Database Serverless is a compute tier for single databases that automatically scales compute based on workload demand, and bills for the amount of compute used per second. The serverless compute tier also automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns.
2020

2121
Once you have followed the below steps, your database will be migrated into Azure SQL Database Serverless, enabling you to make your database available to other users or applications in the cloud and only pay for what you use, with minimal application code changes.
2222

@@ -31,7 +31,7 @@ Once you have followed the below steps, your database will be migrated into Azur
3131

3232
1. Provision a new Azure SQL Database in the Serverless compute tier.
3333

34-
![screenshot of Azure portal showing provisioning example for azure sql database serverless](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/provision-serverless.png)
34+
![Screenshot of the Azure portal showing provisioning example for Azure SQL Database Serverless](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/provision-serverless.png)
3535

3636
2. Ensure you have your SQLite database file available in your Windows environment. Install a SQLite ODBC Driver if you do not already have one (there are many available in Open Source, for example, http://www.ch-werner.de/sqliteodbc/).
3737

@@ -52,13 +52,13 @@ Once you have followed the below steps, your database will be migrated into Azur
5252

5353
5. Create a new linked service for the source SQLite database in your Data Factory.
5454

55-
![screenshot showing empty linked services blade in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-create.png)
55+
![Screenshot showing empty linked services blade in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-create.png)
5656

57-
6. In Connections, under Linked Service, click New
57+
6. In **Connections**, under **Linked Service**, click **New**.
5858

5959
7. Search for and select the "ODBC" connector
6060

61-
![screenshot showing ODBC connector logo in the linked services blade in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-odbc.png)
61+
![Screenshot showing ODBC connector logo in the linked services blade in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-odbc.png)
6262

6363
8. Give the linked service a meaningful name, for example, "sqlite_odbc". Select your integration runtime from the "Connect via integration runtime" dropdown. Enter the below into the connection string, replacing the Initial Catalog variable with the filepath for the .db file, and the DSN with the name of the system DSN connection:
6464

@@ -70,11 +70,11 @@ Once you have followed the below steps, your database will be migrated into Azur
7070
7171
10. Test the connection
7272
73-
![screenshot showing successful connection in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-test-successful.png)
73+
![Screenshot showing successful connection in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-test-successful.png)
7474
7575
11. Create another linked service for your Serverless SQL target. Select the database using the linked service wizard, and provide the SQL authentication credentials.
7676
77-
![screenshot showing Azure SQL Database selected in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-create-target.png)
77+
![Screenshot showing Azure SQL Database selected in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/linked-services-create-target.png)
7878
7979
12. Extract the CREATE TABLE statements from your SQLite database. You can do this by executing the below Python script on your database file.
8080
@@ -97,7 +97,7 @@ Once you have followed the below steps, your database will be migrated into Azur
9797
9898
14. Return to the home screen of your Data Factory and click "Copy Data" to run through the job creation wizard.
9999
100-
![screenshot showing the Copy Data wizard logo in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/copy-data.png)
100+
![Screenshot showing the Copy Data wizard logo in Azure Data Factory](./media/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial/copy-data.png)
101101
102102
15. Select all tables from the source SQLite database using the check boxes, and map them to the target tables in Azure SQL. Once the job has run, you have successfully migrated your data from SQLite to Azure SQL!
103103

articles/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This article provides answers to frequently asked questions for customers consid
2020
- This FAQ is intended for readers who have a brief understanding of the Hyperscale service tier and are looking to have their specific questions and concerns answered.
2121
- This FAQ isn’t meant to be a guidebook or answer questions on how to use a Hyperscale database. For an introduction to Hyperscale, we recommend you refer to the [Azure SQL Database Hyperscale](service-tier-hyperscale.md) documentation.
2222

23-
## General Questions
23+
## General questions
2424

2525
### What is a Hyperscale database
2626

@@ -206,7 +206,7 @@ No. At this time, you can’t move a Hyperscale database to another service tier
206206

207207
### Do I lose any functionality or capabilities after migration to the Hyperscale service tier
208208

209-
Yes. Some of Azure SQL Database features are not supported in Hyperscale yet, including but not limited to long term backup retention. After you migrate your databases to Hyperscale, those features stop working. We expect these limitations to be temporary.
209+
Yes. Some Azure SQL Database features are not supported in Hyperscale yet, including but not limited to long term backup retention. After you migrate your databases to Hyperscale, those features stop working. We expect these limitations to be temporary.
210210

211211
### Can I move my on-premises SQL Server database, or my SQL Server database in a cloud virtual machine to Hyperscale
212212

@@ -241,21 +241,21 @@ SQL Server 2005. For more information, see [Migrate to a single database or a po
241241

242242
Yes. [Azure Database Migration Service](../../dms/dms-overview.md) supports many migration scenarios.
243243

244-
## Business Continuity and Disaster Recovery Questions
244+
## Business continuity and disaster recovery questions
245245

246246
### What SLAs are provided for a Hyperscale database
247247

248248
See [SLA for Azure SQL Database](https://azure.microsoft.com/support/legal/sla/sql-database/v1_4/). Additional secondary compute replicas increase availability, up to 99.99% for a database with two or more secondary compute replicas.
249249

250-
### Are the database backups managed for me by the Azure SQL Database service
250+
### Are the database backups managed for me by Azure SQL Database
251251

252252
Yes.
253253

254254
### How often are the database backups taken
255255

256256
There are no traditional full, differential, and log backups for Hyperscale databases. Instead, there are regular storage snapshots of data files. Log that is generated is simply retained as-is for the configured retention period, allowing restore to any point in time within the retention period.
257257

258-
### Does Hyperscale support point in time restore
258+
### Does Hyperscale support point-in-time restore
259259

260260
Yes.
261261

@@ -283,7 +283,7 @@ No. The storage format for Hyperscale databases is different from any released v
283283

284284
### Do I lose any functionality or capabilities after migration to the Hyperscale service tier
285285

286-
Yes. Some of Azure SQL Database features are not supported in Hyperscale, including but not limited to long term backup retention. After you migrate your databases to Hyperscale, those features stop working.
286+
Yes. Some Azure SQL Database features are not supported in Hyperscale, including but not limited to long term backup retention. After you migrate your databases to Hyperscale, those features stop working.
287287

288288
### Will Polybase work with Hyperscale
289289

@@ -295,9 +295,9 @@ Not at this time.
295295

296296
### Are compute nodes containerized
297297

298-
No. Hyperscale processes run on a [Service Fabric](https://azure.microsoft.com/services/service-fabric/) nodes (VMs), not in containers.
298+
No. Hyperscale processes run on [Service Fabric](https://azure.microsoft.com/services/service-fabric/) nodes (VMs), not in containers.
299299

300-
## Performance Questions
300+
## Performance questions
301301

302302
### How much write throughput can I push in a Hyperscale database
303303

0 commit comments

Comments
 (0)