Pls note …
Delete statements will still leave holes opened and db files might not shrink as expected.
Unfortunately SAG has not designed the Transactions tables as DB Partitions …so we can drop the old partitions.
What i used to follow in one of the customer is…
let us say DB has 2 schema A and B with each 1TB size
I would point TN IS to A for 2 months and then take an outage to Point to B … so you can use 2 monitors/mws for transaction checking etc…
Later once you find B getting filled, Truncate all objects in A or (drop and create objects) and take an outage to point IS back to A
So, to conclude following actions on wM txn tables
Delete - Temp. fix
truncate releases space - better
drop and create is - best