It is postgresql.conf setting:
https://www.ibm.com/docs/en/psfa/7.2.1?topic=extents-enabling-random-chunk-distributions
The default value of the system.enableRandomDistributionChunkSize registry variable is no (off).
But again: this is for 7.X (old Netezza).
I believe that this setting is ON by default on NPS (at least 11.2.X)
[nz@dev3majcp4d nz]$ nzsql -c "show enable_random_dist_chunk"
NOTICE: ENABLE_RANDOM_DIST_CHUNK is on
SHOW VARIABLE
------------------------------
Adam Matusewicz
------------------------------
Original Message:
Sent: Wed March 13, 2024 10:00 AM
From: Jackson Eyton
Subject: Percentage limit of NPS total Storage Usage.
Adam, thank you for this reply. Could you clarify a little further on the following:
'Enable Random Dist Chunk'? We use random distribution for nearly all of our tables, most of which are small tables. I've not heard of random dist chunk throughout our years of netezza use, nor even when investigating the immense table size used exapansion that we saw when migrating from on-prem NPS to Azure hosted NPS.
For small tables do not use distribution organization, I assume that means simply use distribute on random? We use datastage to drop and create a good number of our tables with the random distribution set, most everything else is a truncate and load operation, also using distribute on random. We have no specified any organize on properties for tables. Is there an easy way to check what the organize on values are for multiple tables? Is there a size threshold before setting an organize column?
------------------------------
Jackson Eyton
Original Message:
Sent: Tue March 12, 2024 08:08 AM
From: Adam Matusewicz
Subject: Percentage limit of NPS total Storage Usage.
Hi
As far I'm aware there was no limit to Database/Data size in Netezza systems: except physical storage capacity.
Since NPS / (CP4D) share vast majority of the code with Netezza: I presume it's the same.
That is why is so important to keep your data "clean":
- groom tables (with proper backup/groom sequence or just go for BACKUPSET NONE)
- use distribute on random and enable random dist chunk
- for small tables do not use distribution organization (otherwise will use 3MB on every dataslice)
- developers have nasty tendency to spawn objects (tables) everywhere: drop those on sight (if nobody admit using it: check first in HISTDB what/who/why?)
------------------------------
Adam Matusewicz
Original Message:
Sent: Wed February 07, 2024 06:26 AM
From: Andrea Ceccotti
Subject: Percentage limit of NPS total Storage Usage.
Hi All,
Is there a limit on the Total Storage Usage Percentage on NPS? Below which it is not possible to go down?
On my NPS Production Environment by executing the command /nz/support/bin/nz_storage_stats
it results Remaining about 19%
Total Storage
Available (TiB) 134.128
.....
.................
Remaining (%) 19.065
Which is the Percentage limit?
Thanks all.
Bye
Andrea
------------------------------
Andrea Ceccotti
------------------------------