Also keep in mind that the B tables have sub tables if you actually have any attachments. You will find B<schema ID>H<field ID>,
If you don't catch those also you might find yourself with some data left over. HTH, Brian Goralczyk On Thu, Jan 9, 2014 at 3:02 PM, Grooms, Frederick W < frederick.w.gro...@xo.com> wrote: > ** > > We do it with a truncate table SQL command (since we want to delete > everything) > > Simply find your schema ID for the form in question and Truncate the T, H, > and B tables for that ID > > > > Fred > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Cecil, Ken > *Sent:* Thursday, January 09, 2014 2:58 PM > *To:* arslist@ARSLIST.ORG > > *Subject:* Cleaning up forms before migration > > > > ** > > We have some backend forms with large amounts of data that we don’t care > about and would like to delete before doing a data migration. > > > > For example FB:History has over 160 million records. What is the best way > to go about deleting data out of the forms that have gotten away from us. > > > > I know we should have set up escalations or archiving to prevent this. > > > > Obviously deleting them through search and delete is out of the question. > If I set up an escalation to do it I think it would kill performance or > take forever. How do you guys go about it. Risky SQL? > > > > Thanks, > > > > Ken Cecil > > > > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"