# Tessell DBaaS *Last update: November 15, 2024* **Note** AWS Partner product descriptions and reported qualifications, including compliance, are provided by the AWS Partner and are not verified by AWS. For more information about these products, contact the AWS Partner. You are encouraged to conduct your own additional due diligence before choosing to use any of the products listed. ## Product overview | | | Category | Product capabilities | | --- |--- | | **Product website** | [Tessell](https://www.tessell.com/) | | **Product certifications**
[AWS Competency Program](https://aws.amazon.com/partners/offerings/) competencies and other certifications | Migration and Modernization ISV Competency | | **AWS Marketplace**
Link to subscribe or download | [Tessell DBaaS on AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-h2caqujt4pp3q) | | **Tool deployment model**
Product can be SaaS-based or customer-deployed | SaaS on AWS (vendor VPC) Servers deployed on AWS (customer VPC) SaaS or servers in other cloud provider environment | | **Compliance** | International Organization for Standardization (ISO) 27001 and 27701 Payment card industry (PCI) System and Organization Controls (SOC) | | **Service model** | Full self-service – Deployment, management, and maintenance can be done by the customer or end-user Self-service with vendor support – Deployment, management, and maintenance can be done by customer or end-user with the option of vendor support | | **Pricing model** | Subscription | ## Data migration | | | Category | Product capabilities | | --- |--- | | **Replication method**
The ability to support one or more of the following replication methods: Agentless – Uses protocols or interfaces such as SNMP or WMI Agent-based – Requires installation of software on the source resources, such as Linux or Windows servers Login-based – Uses protocols, such as SSH and RDP, to log in to the source servers | Login-based | | **Replication source**
Support for one or more of the following sources: Block File Object Tape Other | Block File | | **Automation**
The ability to manage a migration through scheduling controls: Product can be accessed, configured, and managed programmatically Product can schedule migration jobs Product can pause and resume migrations Product can schedule bandwidth throttling (for example, to increase throughput during off-peak periods) | Access programmatically Schedule migrations Pause and resume migration Schedule bandwidth throttling | | **Performance**
The ability to optimize performance: Manage bandwidth consumption, such as through throttling Compress data before transfer to reduce network traffic Run multithreaded or concurrent process for data migration tasks | Managed bandwidth consumption Compression before transfer Multithreaded or concurrent process support | | **Security**
The ability to secure the product and data transfers: Encrypt data in transit from source to destination Support the use of customer-provided encryption keys Store all actions requested by the user and performed by the tool in a tamper-proof audit log Integrate with third-party identity providers for authentication | Encrypt data in transit from source to destination Support the use of customer-provided encryption keys Store all actions requested by the user and performed by the tool in a tamper-proof audit log Integrate with third-party identity providers for authentication | | **Synchronization type**
The ability to support multiple data-synchronization options: One-time transfer Periodic transfer Continuous transfer | One-time transfer Periodic transfer Continuous transfer | | **File-transfer options**
The ability to support file migration options: Track all files copied previously and compare against source data in the subsequent copy Copy only modified portions of a file instead of the entire file Support include or exclude patterns for copying files and folders with simple or regular expression patterns | Changed-file tracking Copy for only modified portions of a file | | **NFS and SMB options**
For Network File System (NFS) and Server Message Block (SMB) file systems, the ability to do the following: Preserve symbolic link Preserve hard link Move open files | Not available | | **Data validation**
The ability to validate data transfers by using checksums for data integrity | Available | | **Discovery**
The ability to scan and report on source system data (such as file name, type, size, usage, file timestamps, and summary statistics) and produce a pre-migration assessment report | Available | | **Reporting and alerting**
The ability to report on data-transfer progress and statistics: File and object transfer statistics Network statistics Time and duration statistics, including time taken and forecast completion Generation of a detailed post-migration report Generation of a full validation report after migration completion Alerting on failure scenarios, job completion | File and object transfer statistics Time and duration statistics, including time taken and forecast completion Generation of a detailed post-migration report Generation of a full validation report after migration completion Alerting on failure scenarios, job completion | | **Failure handling**
The ability to retry transfer operations if a network failure or connectivity issue occurs | Available | ## Database migration | | | Category | Product capabilities | | --- |--- | | **Migration approach** Homogeneous – Source and target engine are the same Heterogeneous – Source and target engine are different The ability to convert source database engine metadata to be compatible with the target database engine The ability of the tool to migrate large database objects, such as LOB and binary data types | Homogeneous Support for LOB data types, including BLOB, CLOB, NCLOB, and BFILE | | **Source engine**
The ability to migrate specific database engines, such as IBM Db2 LUW, MariaDB, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, or others | MariaDB Microsoft SQL Server Milvus MongoDB MySQL Oracle PostgreSQL | | **Migration type** Full load only – Perform a one-time migration from source to target Full load with CDC – Perform full load with change data capture (CDC) to continue replication from source to target CDC only – Don't perform a one-time migration, but continue to replicate data changes from the source to the target Offline – Migrate large data sets by using offline methods or external storage devices | Full load with CDC Offline | | **Data transform**
The ability to transform data during the migration | Metadata Table data | | **Migration scope**
The ability to migrate metadata and application data: Metadata – Migrate database schema structure, including table, view, and stored procedure definition Table data – Migrate table data | Metadata Table data | | **Tool architecture, high availability**
The ability support one or more of the following high availability (HA) configurations: Built-in HA configuration Manual HA configuration | Built-in HA configuration | | **Tool sizing**
The ability to size itself for the migration load: Intelligent sizing during discovery Manual sizing based on source database parameters, such as database size or change log | Intelligent sizing Manual sizing | | **Data-type support**
The ability to migrate standard and custom data types | Standard Custom | | **Pre-migration assessment**
The ability to assess and warn of potential migration issues before starting the migration task | Available | | **Data validation**
The ability to compare the data at the source and the target immediately after it performs a full data load | Available for all tables | | **Monitoring and logging**
The ability to log and monitor the migration task and monitor tool performance | Task logging Task monitoring and alerts Performance monitoring | | **Security**
The ability to retain data encryption (if any) from source to target | Available | | **Data selection**
The ability to migrate a subset of data | Available | | **Migration parallelism**
The ability to migrate multiple subsets of data in parallel | Available. Multiple degrees of parallelism can be achieved when taking an [RMAN backup](https://docs.oracle.com/en/database/oracle/oracle-database/12.2/bradv/configuring-rman-client-advanced.html).
After the backup is restored, the subsequent data transfer through Oracle DataGuard happens serially in the order that the transactions were executed. The transfer is done this way so that the database at the destination always remains consistent and readable. |