As an alternative to DAF deployment, ATG Content Administration provides a mechanism called direct SQL deployment, which transfers data between source and target databases using distributed SQL statements. Direct SQL deployment is faster and scales better for large deployments than DAF deployment. Note, however, that direct SQL deployment is supported only on Oracle and Microsoft SQL Server databases, and only for specific configurations:
On Oracle databases, direct SQL deployment can be used for both full and incremental deployments.
On Microsoft SQL Server databases, direct SQL deployment can be used for full deployments only. Incremental deployments use DAF deployment.
Direct SQL deployment does not apply to file assets. If you use direct SQL deployment for repository assets, file assets are deployed using DAF deployment.
If your publishing and production database schemas are on different machines, you must set up database links (Oracle) or linked servers (Microsoft SQL Server) between the machines. For information about setting up ATG Content Administration to use direct SQL deployment, see Configure Direct SQL Deployment.