Skip to content
This repository was archived by the owner on Nov 12, 2024. It is now read-only.

Commit 6f00963

Browse files
1 parent 6ef972e commit 6f00963

7 files changed

+12
-24
lines changed

docs/imports/amazon-aurora-migration-guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ If your database uses foreign key constraints, we will detect them after success
101101

102102
![The box showing you are successfully connected, ready to import rows, and have foreign key constraints](/assets/docs/imports/amazon-aurora-migration-guide/successfully-connected-box.jpg)
103103

104-
If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Continue import**” to migrate your data to PlanetScale.
104+
If the connection is successful, click “**Continue import**” to migrate your data to PlanetScale.
105105

106106
{% callout type="warning" %}
107107
If you receive an error, check the [Troubleshooting](#troubleshooting) section for information on correcting common configuration issues.

docs/imports/aws-rds-migration-guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ The “**Connect to database**” button will update with the connection status.
8989
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support for your database.
9090
{% /callout %}
9191

92-
If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Begin database import**” to migrate your data to PlanetScale.
92+
If the connection is successful, click “**Begin database import**” to migrate your data to PlanetScale.
9393

9494
{% callout type="warning" %}
9595
If you receive an error, check the [Troubleshooting](#troubleshooting) section for information on correcting common configuration issues.

docs/imports/azure-database-for-mysql-migration-guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ The “**Connect to database**” button will update with the connection status.
8989
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support for your database.
9090
{% /callout %}
9191

92-
If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Begin database import**” to migrate your data to PlanetScale.
92+
If the connection is successful, click “**Begin database import**” to migrate your data to PlanetScale.
9393

9494
The following view will show you the progress of your data being imported.
9595

docs/imports/database-imports.md

+6-18
Original file line numberDiff line numberDiff line change
@@ -22,14 +22,8 @@ To import an existing database into PlanetScale:
2222

2323
1. Head to your PlanetScale dashboard and click on "**New database**" > "**Import database**," which will bring you to the **Import Setup page**.
2424
2. Give your imported database a name and [select a region](/docs/concepts/regions) from the dropdown.
25-
3. Add a credit card to your organization. You will only be charged if your import requires a Scaler Pro plan (for imports that use over 5 GB of storage), and we will ask you to confirm before proceeding.
26-
4. We recommend using the same name as the database you're importing from to avoid updating any database name references throughout your application code. If you'd prefer to use a different database name, make sure to update your app where applicable once you fully switch over to PlanetScale.
27-
28-
{% callout %}
29-
Importing a database will **not** count towards your `read` or `write` usage.
30-
{% /callout %}
31-
32-
5. Fill in the following connection values with information from your existing hosted database:
25+
3. We recommend using the same name as the database you're importing from to avoid updating any database name references throughout your application code. If you'd prefer to use a different database name, make sure to update your app where applicable once you fully switch over to PlanetScale.
26+
4. Fill in the following connection values with information from your existing hosted database:
3327

3428
- **Host name** — The address where the database is hosted.
3529
- **Port** — The port where your database is hosted. The default MySQL port is `3306`.
@@ -42,16 +36,16 @@ To import an existing database into PlanetScale:
4236
database you're importing.
4337
{% /callout %}
4438

45-
6. You'll have the option to **Authenticate with password** or **Authenticate with mTLS**. To authenticate with a password, type in the password for the username you entered. Make sure the user has `read` and `write` access to this database.
39+
5. You'll have the option to **Authenticate with password** or **Authenticate with mTLS**. To authenticate with a password, type in the password for the username you entered. Make sure the user has `read` and `write` access to this database.
4640

4741
For the "Authenticate with mTLS option," you'll need to provide the following:
4842

4943
- **SSL client certificate** — Certificate to authenticate PlanetScale with your database server.
5044
- **SSL client key** — This is the private key for the client certificate
5145

52-
7. From here, you can proceed to [testing the connection](#test-the-connection) or click "**Show advanced settings**" for more options.
46+
6. From here, you can proceed to [testing the connection](#test-the-connection) or click "**Show advanced settings**" for more options.
5347

54-
8. (Optional) Under Advanced settings, you have the option to enter the following:
48+
7. (Optional) Under Advanced settings, you have the option to enter the following:
5549

5650
- **SSL server name override**
5751
- **SSL CA certificate chain** — If your database server provides a certificate with a non-trusted root CA, please provide the full CA certificate chain here.
@@ -66,16 +60,10 @@ To import an existing database into PlanetScale:
6660
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support for your database.
6761
{% /callout %}
6862

69-
2. If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Begin database import**” to start migrating your data to PlanetScale.
63+
2. If the connection is successful, click “**Begin database import**” to start migrating your data to PlanetScale.
7064

7165
Or, if the connection fails, you'll get an error message in the dashboard. Double-check your connection information or see our [Troubleshooting section](#troubleshooting-connectivity-issues) for more information.
7266

73-
### Importing large databases
74-
75-
If you're importing a large database (that uses over 5 GB of storage) and have not added billing information to your Organization, you will receive a prompt to upgrade your plan. You can use the **Add new card** button to add a credit card and upgrade your account.
76-
77-
Once you've successfully upgraded your plan, you should be able to continue importing your external database into PlanetScale.
78-
7967
## Foreign key constraints
8068

8169
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support.

docs/imports/digitalocean-database-migration-guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ The “**Connect to database**” button will update with the connection status.
9797
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support for your database.
9898
{% /callout %}
9999

100-
If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Begin database import**” to migrate your data to PlanetScale.
100+
If the connection is successful, click “**Begin database import**” to migrate your data to PlanetScale.
101101

102102
You’ll then be moved to a page where you can monitor the import status of the database from DigitalOcean.
103103

docs/imports/gcp-cloudsql-migration-guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ The “**Connect to database**” button will update with the connection status.
8181
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support for your database.
8282
{% /callout %}
8383

84-
If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Begin database import**” to migrate your data to PlanetScale.
84+
If the connection is successful, click “**Begin database import**” to migrate your data to PlanetScale.
8585

8686
The following view will show you the progress of your data being imported.
8787

docs/imports/mariadb-migration-guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ The “**Connect to database**” button will update with the connection status.
107107
If your database uses foreign key constraints, we will detect them after successfully connecting to your external database and automatically enable foreign key constraint support for your database.
108108
{% /callout %}
109109

110-
If the connection is successful and plan upgrades are complete (if the database is over 5 GB), click “**Begin database import**” to migrate your data to PlanetScale.
110+
If the connection is successful, click “**Begin database import**” to migrate your data to PlanetScale.
111111

112112
If the connection was successful, you’ll see the following message. Click “**Begin database import”** to start importing data.
113113

0 commit comments

Comments
 (0)