Hi, I've truncated a table on my dev server and started a DTS import to copy records from production. I notice that DTS has a habit of zipping thru the file copy then apparently stopping for a while and then declaring it's done. Is DTS doing something clever like dropping table indexes and then re-creating them after the records are copied? If so, how does it remember what the indexes were so it can reinstate them? Is there any way we could also take advantage of this mechanism outside of DTS?