Direct or Runtime Deployment
As of Privacy version 3.8.0 there is a distinction between Direct Deployment and Runtime Deployment.
Direct Deployment means that you create and develop your data masking project in DATPROF Privacy and deploy it using DATPROF Privacy as well.
Runtime Deployment means that you create and develop your data masking project in DATPROF Privacy and deploy it using DATPROF Runtime.
As of Privacy version 4.0 Direct Deployment has been changed to use an embedded Runtime Agent by default. This means that the same package is generated as with Runtime Deployment but instead of uploading this package to DATPROF Runtime, a local agent is started that will execute the package directly. One major benefit of this new direct deployment scheme is that PostgreSQL is now supported with Direct Deployment.
As of version 4.15.0 of Privacy, the Use legacy deployment option in the Project menu has been removed.
Direct Deployment | Direct Deployment (legacy) | Runtime Deployment | |
---|---|---|---|
Oracle | x | x | x |
MS SQL Server | x | x | x |
DB2 i | x | x | x |
DB2 Luw | x | x | x |
PostgreSQL | x | x | |
MySQL / MariaDB | x | x | |
Azure SQL | x | x |