# Case-Management-Table can't have more than 1600 columns **URL:** \ **Category:** General\ **Created:** [September 12, 2026, 6:05am UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447 "2026-09-12T06:05:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![SowdhaminiR](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@SowdhaminiR](https://forums.pega.com/u/SowdhaminiR)\ **Post date:** [September 12, 2026, 6:05am UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/1 "2026-09-12T06:05:00Z")
Hi, I see someone else in this → [Pega 8.5 error : Table can’t have more than 1600 columns](https://forums.pega.com/t/pega-8-5-error-table-cant-have-more-than-1600-columns/1519 "https://forums.pega.com/t/pega-8-5-error-table-cant-have-more-than-1600-columns/1519") 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. ---
**Author:** ![Will\_Cho](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/will_cho/32/23260_2.png) [@Will\_Cho](https://forums.pega.com/u/Will_Cho)\ **Post date:** [September 14, 2026, 12:48pm UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/2 "2026-09-14T12:48:21Z")
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. ---
**Author:** ![RameshSangili](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/rameshsangili/32/23377_2.png) [@RameshSangili](https://forums.pega.com/u/RameshSangili)\ **Post date:** [September 15, 2026, 1:07am UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/3 "2026-09-15T01:07:26Z")
> [@SowdhaminiR](#): > > Hi, I see someone else in this → [Pega 8.5 error : Table can’t have more than 1600 columns](https://forums.pega.com/t/pega-8-5-error-table-cant-have-more-than-1600-columns/1519 "https://forums.pega.com/t/pega-8-5-error-table-cant-have-more-than-1600-columns/1519") 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. 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. ---
**Author:** ![SowdhaminiR](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@SowdhaminiR](https://forums.pega.com/u/SowdhaminiR)\ **Post date:** [September 15, 2026, 4:57pm UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/4 "2026-09-15T16:57:41Z")
In my end, after deleting the unused columns, still in the questionnaire type not able to create the properties, and showing the below error. ![2026-09-11_17h30_12](https://pega1.discourse-cdn.com/pega/original/3X/9/d/9de552f1dd303350c08bdeab731c187583865d89.png) ---
**Author:** ![Will\_Cho](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/will_cho/32/23260_2.png) [@Will\_Cho](https://forums.pega.com/u/Will_Cho)\ **Post date:** [September 15, 2026, 6:50pm UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/5 "2026-09-15T18:50:28Z")
@SowdhaminiR i would try restarting the server (if not already) and test again. ---
**Author:** ![RameshSangili](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/rameshsangili/32/23377_2.png) [@RameshSangili](https://forums.pega.com/u/RameshSangili)\ **Post date:** [September 15, 2026, 11:29pm UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/6 "2026-09-15T23:29:19Z")
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? ---
**Author:** ![SowdhaminiR](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@SowdhaminiR](https://forums.pega.com/u/SowdhaminiR)\ **Post date:** [September 17, 2026, 4:06am UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/7 "2026-09-17T04:06:17Z")
It is in pega cloud, no im not yet to check with DBA team. It’s one of the possible solution im right? ---
**Author:** ![SowdhaminiR](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@SowdhaminiR](https://forums.pega.com/u/SowdhaminiR)\ **Post date:** [September 17, 2026, 4:06am UTC](https://forums.pega.com/t/case-management-table-cant-have-more-than-1600-columns/13447/8 "2026-09-17T04:06:50Z")
Okay let me try, thanks will Cho