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
Customer ran EXPORT_PATH and noticed it consumes a lot of network bandwidth with default auto parallelism settings.
In general one can try to follow Export Parallelism Parameter. However, it will be great to know the real parallelism settings calculated by the DB, to use it as a starting point.
Currently this information could only be pulled from remote logs or SQL logs. Both aren't documented / supposed to be read by users.
Please consider making the real calculated parallelism for IMPORT_PATH and EXPORT_PATH available in any public location (say, in a system table).
The text was updated successfully, but these errors were encountered:
Customer ran EXPORT_PATH and noticed it consumes a lot of network bandwidth with default auto parallelism settings.
In general one can try to follow Export Parallelism Parameter. However, it will be great to know the real parallelism settings calculated by the DB, to use it as a starting point.
Currently this information could only be pulled from remote logs or SQL logs. Both aren't documented / supposed to be read by users.
Please consider making the real calculated parallelism for IMPORT_PATH and EXPORT_PATH available in any public location (say, in a system table).
The text was updated successfully, but these errors were encountered: