I believe each DDL file represents one <model> element in the vdb.xml file.
1 of 1 people found this helpful
Yes, you can use a separate DDL per model/schema. It makes very little difference other than naming (which can impact how permissions are specified) to split virtual models. If you split a physical model the same caveat applies about naming, and then as long as the translator/connection name are the same the optimizer will treat the models as the same for optimization purposes.