You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This article walks through the basic considerations that a developer should be aware of when writing code to connect to your database in Azure. This article applies to Azure SQL Database, and Azure SQL Managed Instance
18
-
17
+
This article walks through the basic considerations that a developer should be aware of when writing code to connect to your database in Azure. This article applies to Azure SQL Database, and Azure SQL Managed Instance.
19
18
20
19
## Language and platform
21
20
22
-
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.
21
+
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.
23
22
24
23
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.
25
24
26
25
## Authentication
27
26
28
-
Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database supports both SQL Server and [Azure Active Directory (AAD) authentication](authentication-aad-overview.md) users and logins. AAD logins are available only in SQL Managed Instance.
27
+
Access to Azure SQL Database is protected with logins and firewalls. Azure SQL Database supports both SQL Server and [Azure Active Directory authentication](authentication-aad-overview.md) users and logins. Azure Active Directory logins are available only in SQL Managed Instance.
29
28
30
29
Learn more about [managing database access and login](logins-create-manage.md).
31
30
@@ -39,7 +38,7 @@ Avoid long-running transactions because any infrastructure or connection failure
39
38
40
39
## Resiliency
41
40
42
-
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).
41
+
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).
43
42
44
43
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).
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
88
88
89
89
For more information about changing connection strings, see the appropriate development language for your [connection library](connect-query-content-reference-guide.md#libraries).
90
90
91
-
### Configure Firewall Rules
91
+
### Configure firewall rules
92
92
93
93
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).
Copy file name to clipboardExpand all lines: articles/azure-sql/database/migrate-sqlite-db-to-azure-sql-serverless-offline-tutorial.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.custom: sqldbrb=1
17
17
18
18
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.
19
19
20
-
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.
20
+
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.
21
21
22
22
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.
23
23
@@ -32,7 +32,7 @@ Once you have followed the below steps, your database will be migrated into Azur
32
32
33
33
1. Provision a new Azure SQL Database in the Serverless compute tier.
34
34
35
-
35
+
36
36
37
37
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/).
38
38
@@ -53,13 +53,13 @@ Once you have followed the below steps, your database will be migrated into Azur
53
53
54
54
5. Create a new linked service for the source SQLite database in your Data Factory.
55
55
56
-
56
+
57
57
58
-
6. In Connections, under Linked Service, click New
58
+
6. In **Connections**, under **Linked Service**, click **New**.
59
59
60
60
7. Search for and select the "ODBC" connector
61
61
62
-
62
+
63
63
64
64
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:
65
65
@@ -71,11 +71,11 @@ Once you have followed the below steps, your database will be migrated into Azur
71
71
72
72
10. Test the connection
73
73
74
-
74
+
75
75
76
76
11. Create another linked service for your Serverless SQL target. Select the database using the linked service wizard, and provide the SQL authentication credentials.
77
77
78
-
78
+
79
79
80
80
12. Extract the CREATE TABLE statements from your SQLite database. You can do this by executing the below Python script on your database file.
81
81
@@ -98,7 +98,7 @@ Once you have followed the below steps, your database will be migrated into Azur
98
98
99
99
14. Return to the home screen of your Data Factory and click "Copy Data" to run through the job creation wizard.
100
100
101
-
101
+
102
102
103
103
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!
Copy file name to clipboardExpand all lines: articles/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ This article provides answers to frequently asked questions for customers consid
20
20
- 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.
21
21
- 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.
22
22
23
-
## General Questions
23
+
## General questions
24
24
25
25
### What is a Hyperscale database
26
26
@@ -86,7 +86,7 @@ Hyperscale provides rapid scalability based on your workload demand.
86
86
87
87
Provisioning of each of these additional compute replicas can be done in constant time and is an online operation. You can connect to these additional read-only compute replicas by setting the `ApplicationIntent` argument on your connection string to `ReadOnly`. Any connections with the `ReadOnly` application intent are automatically routed to one of the additional read-only compute replicas.
88
88
89
-
## Deep Dive Questions
89
+
## Deep dive questions
90
90
91
91
### Can I mix Hyperscale and single databases in a single server
92
92
@@ -114,7 +114,7 @@ If you are currently running interactive analytics queries using SQL Server as a
114
114
115
115
If you are running data analytics on a large scale with complex queries and sustained ingestion rates higher than 100 MB/s, or using Parallel Data Warehouse (PDW), Teradata, or other Massively Parallel Processing (MPP) data warehouses, SQL Data Warehouse may be the best choice.
116
116
117
-
## Hyperscale Compute Questions
117
+
## Hyperscale compute questions
118
118
119
119
### Can I pause my compute at any time
120
120
@@ -140,7 +140,7 @@ However, if there’s only one replica, it may take some time to build the local
140
140
141
141
For mission-critical apps that require high availability with minimal failover impact, you should provision at least 2 compute replicas including the primary compute replica. This is the default configuration. That way there is a hot-standby replica available that serves as a failover target.
142
142
143
-
## Data Size and Storage Questions
143
+
## Data size and storage questions
144
144
145
145
### What is the maximum database size supported with Hyperscale
146
146
@@ -194,7 +194,7 @@ Yes, including row, page, and columnstore compression.
194
194
195
195
Yes. The data pages associated with a given table can end up in multiple data files, which are all part of the same filegroup. SQL Server uses [proportional fill strategy](https://docs.microsoft.com/sql/relational-databases/databases/database-files-and-filegroups#file-and-filegroup-fill-strategy) to distribute data over data files.
196
196
197
-
## Data Migration Questions
197
+
## Data migration questions
198
198
199
199
### Can I move my existing databases in Azure SQL Database to the Hyperscale service tier
200
200
@@ -206,7 +206,7 @@ No. At this time, you can’t move a Hyperscale database to another service tier
206
206
207
207
### Do I lose any functionality or capabilities after migration to the Hyperscale service tier
208
208
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.
210
210
211
211
### Can I move my on-premises SQL Server database, or my SQL Server database in a cloud virtual machine to Hyperscale
212
212
@@ -241,21 +241,21 @@ SQL Server 2005. For more information, see [Migrate to a single database or a po
241
241
242
242
Yes. [Azure Database Migration Service](../../dms/dms-overview.md) supports many migration scenarios.
243
243
244
-
## Business Continuity and Disaster Recovery Questions
244
+
## Business continuity and disaster recovery questions
245
245
246
246
### What SLAs are provided for a Hyperscale database
247
247
248
248
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.
249
249
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
251
251
252
252
Yes.
253
253
254
254
### How often are the database backups taken
255
255
256
256
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.
257
257
258
-
### Does Hyperscale support point in time restore
258
+
### Does Hyperscale support point-in-time restore
259
259
260
260
Yes.
261
261
@@ -279,11 +279,11 @@ Not at this time.
279
279
280
280
No. The storage format for Hyperscale databases is different from any released version of SQL Server, and you don’t control backups or have access to them. To take your data out of a Hyperscale database, you can extract data using any data movement technologies, i.e. Azure Data Factory, Azure Databricks, SSIS, etc.
281
281
282
-
## Cross-Feature Questions
282
+
## Cross-feature questions
283
283
284
284
### Do I lose any functionality or capabilities after migration to the Hyperscale service tier
285
285
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.
287
287
288
288
### Will Polybase work with Hyperscale
289
289
@@ -295,9 +295,9 @@ Not at this time.
295
295
296
296
### Are compute nodes containerized
297
297
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.
299
299
300
-
## Performance Questions
300
+
## Performance questions
301
301
302
302
### How much write throughput can I push in a Hyperscale database
303
303
@@ -319,7 +319,7 @@ Because the storage is shared and there is no direct physical replication happen
319
319
320
320
For most performance problems, particularly the ones not rooted in storage performance, common SQL diagnostic and troubleshooting steps apply. For Hyperscale-specific storage diagnostics, see [SQL Hyperscale performance troubleshooting diagnostics](hyperscale-performance-diagnostics.md).
321
321
322
-
## Scalability Questions
322
+
## Scalability questions
323
323
324
324
### How long would it take to scale up and down a compute replica
325
325
@@ -345,7 +345,7 @@ Yes. The `tempdb` database will scale up automatically as the compute grows.
345
345
346
346
No. Only the primary compute replica accepts read/write requests. Secondary compute replicas only accept read-only requests.
347
347
348
-
## Read Scale-out Questions
348
+
## Read scale-out questions
349
349
350
350
### How many secondary compute replicas can I provision
351
351
@@ -385,6 +385,6 @@ No. Hyperscale databases have shared storage, meaning that all compute replicas
385
385
386
386
Data latency from the time a transaction is committed on the primary to the time it is visible on a secondary depends on current log generation rate. Typical data latency is in low milliseconds.
387
387
388
-
## Next Steps
388
+
## Next steps
389
389
390
390
For more information about the Hyperscale service tier, see [Hyperscale service tier](service-tier-hyperscale.md).
0 commit comments