This repository was archived by the owner on Dec 6, 2023. It is now read-only.
Update sample import script to use a valid value for MaxSizeBytes #340
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The value previously in use (262144000, which is 250MB) is not a valid size for an S3 database. Trying to create a database of that size will throw an error like `The edition 'Standard' does not support the database data max size '262144000'.` I am not clear whether 250MB was *ever* a valid size for S3, but it certainly is not now. It used to be the case that the Import/Export service would silently swallow this error and just create a database of the max size for the SLO. However, that (buggy) behavior was fixed around November 2020 to respect the parameter.
|
#sign-off |
|
@mikefrobbins - I see another PR pinged you to merge. Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The value previously in use (262144000, which is 250MB) is not a valid size for an S3 database. Trying to create a database of that size will throw an error like
The edition 'Standard' does not support the database data max size '262144000'.I am not clear whether 250MB was ever a valid size for S3, but it certainly is not now. It used to be the case that the Import/Export service would silently swallow this error and just create a database of the max size for the SLO. However, that (buggy) behavior was fixed around November 2020 to respect the parameter.
Checklist
Testing information
Platform and PowerShell version: 10.0.19041.906, 5.1.19041.906
Az version: 5.2.0