We are on a very recent Pega Cloud install. We have a years-old work history table with an empty pzpvstream column. It looks like new History- tables dispensed with the column long ago. The column is preventing me from running an BIX extract against it. It there any reason not to drop its pzpvstream?
Hello @mjosborn85
While reviewing our content with no replies I came across your question. I’m not sure if you have resolved this on your own or are still looking for assistance.
If you are still looking for assistance, I’d like to direct you to our new Pega As-a-Service Expert Circle that we launched at PegaWorld this year! Our Expert Circle leaders will be able to assist you over there.
Please repost your question in our Expert Circle or share the resolution here.
If you repost your question, do let me know and I can make sure our leaders see it!
Thank you!
dropping an always-empty pzpvstream from a History- table is generally safe, because modern Pega writes history as exposed columns and does not use a BLOB there. Do this cleanly: first verify it’s truly unused with a quick check (count rows where pzpvstream is not null and length > 0 is zero). Confirm no reports/BIX extracts/reference rules explicitly point to pzpvstream, and that your History- class is mapped to this table (Data-Admin-DB-Table) with only exposed columns. Take a backup and test in lower environments; run your BIX extract after the change. On Pega Cloud, raise a schema change ticket and have Pega Cloud Ops execute the ALTER TABLE drop column during a window. If you can’t change the table, create a DB view that omits pzpvstream, map a temporary class to that view, and run BIX from the temp class. Either way, once validated, promote the change and you’re done.