1.
What is Daffodil Replicator (E)? 2.
How long does it take to install Daffodil Replicator (E)? 3.
How much hard drive space does Daffodil Replicator (E) require? 4.
What are the minimum and recommended configurations of Replicator and Replication DataSource? 5.
Which Replicator and Replication DataSource platforms are supported by Daffodil Replicator (E)? 6.
Does Daffodil Replicator (E) supports networked, Internet, and remote users? 7.
Does Daffodil Replicator (E) contain wizards that help me in configuring a datasource?
1. What is Daffodil Replicator (E)?
Daffodil Replicator (E) is a Java tool for data synchronization, data integration, data migration, and data backup between various database servers. Daffodil Replicator supports following databases: Microsoft SQL Server, Oracle, Daffodil DB, DB2, Derby, MySql, PostGreSql, Firebird.
Daffodil Replicator can support any database that comes with JDBC connectivity. You can send the request for the support of any other database, which is currently not supported by Daffodil Replicator, through user forum.
2. How long does it take to install Daffodil Replicator (E)?
There is no need for separate installation of Daffodil Replicator. You need to download Daffodil Replicator. After downloading, include the driver jars (in which you want to perform replication) in the lib folder and start the . bat/.sh file.
3. What is the minimum hardware configuration for Daffodil Replicator (E)?
Processor - Celeron 700MHz
RAM - 128 MB
Hard Drive Space - For Replicator 8.14 MB and Replication DataSource 6.84 MB
4. Which platforms are supported by Daffodil Replicator (E)?
Daffodil Replicator (E) is a Java-based tool. Therefore, it is platform independent.
5. Does Daffodil Replicator (E) support networked, Internet, and remote users?
Yes, Daffodil Replicator (E) supports networked, Internet, and remote users.
6. Does Daffodil Replicator (E) contain wizards that help me in configuring a datasource?
Yes, you can refer the Getting Started Guide that includes wizards, which helps you in configuring a datasource.