Yellowbrick has been designed to make migrating from Netezza fast and simple.
From a system perspective, Yellowbrick:
From the database software perspective, the picture is similarly compelling. Yellowbrick:
A Yellowbrick Solutions Architect will help you scope and plan your migration as part of a Proof of Concept (POC). Once your POC is complete, your Solutions Architect will then help you migrate your schema, data, application logic, ecosystem tools, and users to the Yellowbrick platform. You'll have a production-ready system installed and running in under a day and will complete your migration within days or weeks. Your post-migration activities are similarly easy: your team will have very little tuning and configuration, will not have to pay for training and certification for a new system, and can get back to day-to-day business quickly.
What's more, Yellowbrick has improved on Netezza in many areas. It offers superior concurrent and mixed workload support so your apps and databases will run at top speed. Database administration is also much easier: you will not need to groom or vacuum tables, and statistics are automatically gathered and kept up-to-date.
Yellowbrick is also easy to grow. You can scale compute and storage capacity incrementally by adding more blades to the system, up to nearly 1PB of raw storage. This makes sizing your environment more about determining your initial storage needs than estimating what you need five years from now.
This document provides an overview of migration tasks, so you can see how easy it is to migrate to Yellowbrick and serves as a guide to further streamline the process.
Yellowbrick can be deployed in under two hours and be production-ready on day one. Its flash-based architecture means no moving parts to fail during transport. A Yellowbrick Solutions Architect will be onsite to install the system for you. Because Yellowbrick delivers up to 1.2PB of user storage in a 6-10U appliance that fits in a standard rack, you can expect to reclaim racks of space in your data center to save money.
Yellowbrick supports organizing your data into databases and schemas, just like Netezza and every other PostgreSQL-inspired database. This means you do not have to worry about the migration breaking your applications. You can continue to maintain your database organization as you always have, with one database per tenant. If you want to expand to multiple schemas in a single database, you can do so easily.
Yellowbrick includes a query history database that is installed and fully documented. Your queries will be logged and optimized on day one, and you no longer have to endure dumps of in-memory query history or manually configure the NZ_QUERY_HISTORY table as you might have been doing with your Netezza system. Yellowbrick provides a richer, more granular level of detail about all activity within the database and is easy to configure. You can set the retention period for your history with just one click.
The nz_ddl_database command provides all the information about the DDL in your Netezza system, including table, view, synonym, and sequence definitions; user and group role creations; stored procedures; user defined functions; and much more.
To extract the DDL for each database, execute the following command:
$ nz_ddl_database <database> > <database>.ddl
Your Yellowbrick Solutions Architect will perform an inventory of your DDLs and map them appropriately to Yellowbrick, according to best practices, using automated conversion tools.
Migrating your table definitions is a seamless process. Many Yellowbrick customers move the Netezza DDL (CREATE TABLE) with absolutely no change to their data types. In addition, you will have the opportunity to improve your table distribution with the following options:
Yellowbrick also includes the following table features that enable you to further optimize your database:
Because Yellowbrick is based on PostgreSQL, all your valid SQL operations and database views will run as-is.
Yellowbrick supports PL/pgSQL stored procedures. Your Yellowbrick Solutions Architect will perform an impact analysis of your query history to determine which, if any, stored procedures you should migrate (that is, which stored procedures your queries are using).
You export Latin as well as Unicode data from your Netezza system with one of these options:
Exporting Netezza data to CSV files. You can do this on a Windows or Linux client using the following methods:
- SQL for remote external tables
Data will export in ASCII-delimited format that can be compressed.
If you exported the data to a CSV file (as opposed to direct streaming), you will import it using the ybload tool. ybload is intuitive like Netezza nzload , but with dramatic improvements. It is designed for parallelization, so you will not need to chunk files manually, and it easily saturates the 10Gb network connection shipped with Yellowbrick. ybload also compresses data before sending it to Yellowbrick and can load multiple files at once. For example, users can run one ybload with a thousand files as input instead of invoking nzbload a thousand separate times. These optimizations make loading simple and dramatically accelerate load speeds compared to Netezza.
Yellowbrick can also load data directly from cloud-based object storage that's S3-compatible. Compressed or uncompressed files are supported. If you are an HDFS user storing data in Hadoop, Yellowbrick uses a Spark-based importer that can consume most common Hadoop file formats such as Parquet or Avro.
Netezza systems often have an Oracle compatibility toolkit installed that provides a set of UDFs. Typically customers use only a small number of UDFs, and Yellowbrick includes many of these functions out-of-the-box. Your Yellowbrick Solutions Architect will perform an impact analysis to see if there are any functions Yellowbrick does not provide that are being used by queries.
Like Netezza, Yellowbrick supports local or LDAP authentication methods.
Creating database users (or roles) is the primary mechanism for managing local database security. After creating users, you can set up access control by granting or revoking privileges on databases, schemas, tables, columns, and stored procedures. Use the following SQL commands: CREATE ROLE, GRANT, and REVOKE.
Yellowbrick LDAP configurations support directory service providers such as Active Directory (AD) for OpenLDAP. LDAP, LDAPS (LDAP over SSL), and LDAP+TLS configurations. This is an improvement over Netezza LDAP integration, which is limited to just authentication and requires Netezza customers to manually create USERS or GROUPS. This can result in mismatches to the LDAP service.
Yellowbrick provides an alternative to creating non-superusers manually in the database by synchronizing the users and groups stored in an LDAP directory and creates users and roles with the same credentials. You can synchronize specific users and groups by defining search criteria and filters.
You can connect ODBC, JDBC, and ADO.NET applications to a Yellowbrick database using standard PostgreSQL drivers you download and install. This means you do not have to purchase new licenses to redirect your existing applications. More importantly, third-party tools (such as BI, ETL, and analytical tools) that are certified for PostgreSQL drivers will automatically be certified for Yellowbrick.
Yellowbrick ships the open-standard PostgreSQL versions of these Windows or Linux drivers with every system. ETL tools leverage ybload and ybunload for high speed data movement in and out of the Yellowbrick system as described in "Importing Data," above.
As easy as it is to migrate to Yellowbrick, the biggest impact Yellowbrick will have on your organization is after the migration completes . Yellowbrick automates most mundane maintenance tasks so you can free your nights and weekends and finally tackle the projects you've always wanted to.
Yellowbrick is designed to deliver high performance to mixed workloads that modern enterprises require. It can support thousands of concurrent users running mixtures of real-time transactional atomic inserts, bulk loads of data, ELT workloads, interactive queries, ad hoc queries, and long-running, batch-oriented reports.
While today's mixed workloads require a high-performance solution, as the number and diversity of workloads increases, it is even more critical that you have the ability to specify, control, and automate the work that matters most. Yellowbrick gives you this with:
Automating workload management in Yellowbrick is simple and can be done through the Yellowbrick web interface or SQL ALTER commands.
Yellowbrick includes 24x7 predictive remote monitoring technology that enables Yellowbrick Support Engineers to handle day-to-day monitoring activities. Yellowbrick Support Engineers review real-time diagnostic data, provide recommendations, proactively address potential issues, and deliver prompt incident resolution.
You can monitor Yellowbrick yourself, instead of or in addition to the Yellowbrick service. You can do this through automated alerts that easily integrate to the endpoint tool of your choice. This is a welcome relief from manually configuring each nzevent that you want to monitor.
System views give you comprehensive, real-time visibility into the Yellowbrick system. Monitoring is performed continuously without affecting system performance and is thoroughly documented so you can find what you need, when you need to.
Migrating to Yellowbrick from Netezza is fast and painless. In days or weeks you can have a running system that is intuitive like your Netezza system and largely compatible. Better still, your Yellowbrick system will be faster, easier to manage, and incrementally scalable.
To learn more about how Yellowbrick can get you back to business quickly, with a system that is ideal for meeting all your future demands, contact us.