Thanks, @NandiniN, for your response. The requirement here is not about separating the schema, as we are already handling that with direct publishing mode.
The question is whether we can use a single DLT pipeline to execute multiple groups of tables without causing previously created tables to be dropped from Unity Catalog.
For example, in the first DLT run, tables 1-50 are created in Unity Catalog. However, when we use the same DLT pipeline for another set of tables (51-100), the previously created tables (1-50) are dropped, and only tables 51-100 remain in Unity Catalog. We want to prevent this dropping behavior.