Hi, I see someone else in this → Pega 8.5 error : Table can’t have more than 1600 columns facing the same issue. We’re running into the exact same 1600-column error on Postgres, even after deleting a number of columns. If anyone has resolved this and can share the actual steps that worked, please let me know. Thanks in advance.
A table approaching the 1600-column limit might be a sign of a data model issue rather than just a database limitation. From an architectural perspective, I would revisit and question whether all of those properties belong in a single table. How about considering to move related groups of attributes into separate data objects (dedicated data classes) and linking them to the case. If reporting or searchability is required, a Declare Index can be used to expose selected properties into a separate reporting table instead of continuously widening the primary case table.
I think deleting columns and running VACUUM/VACUUM FULL does not reclaim the dropped-column slots. Is this a work table? How it was unnoticed because there will be performance issues due to too many columns.
@SowdhaminiR i would try restarting the server (if not already) and test again.
Is this on Pega Cloud or OnPrem? Check with DBAs if there are any options to recover or raise a SR to Pega Cloud and check suggestions?
It is in pega cloud, no im not yet to check with DBA team. It’s one of the possible solution im right?
Okay let me try, thanks will Cho