Database Migration

SQL Server to Netezza
Case Study

Created by InfoCepts

cost effectively. Netezza appliance supported all the above criteria. hence client introduced it to replace SQL Server. Efficient storage of voluminous data.   Solution Architecture and Approach After studying the challenges and processing needs the problem found was rotating around entire architecture of database and solution was selected based on following criteria     Parallel Processing at database level. daily This was mainly due to execution time spent by database for complex queries retrieving voluminous data and large number of parallel active users to database. Efficient processing of data especially for Data warehouse architecture. However they experienced performance degradation in database as the volume of data and the processing involved started increasing. which processes and loads data into the Data Warehouse. Business Challenges Faced  ETL process slow down Every month there is an ETL run that runs daily for 10 days called Production Cycle. This Production Cycle took almost 6 hrs to complete every day. InfoCepts Case Study Page 2 of 3 . Large number of database objects and complex data storage structures to handle and process voluminous data with maximum efficiency. After this entire production cycle ETL was modified to perform on Netezza DW architecture. Support for Large Parallel connections. who is major data analysis provider for telecom sector. Degrade in Performance of BI Reports used for data quality testing by QC team. The time taken was mostly due to o Heavy processing during ETL on the database server.Database Migration Case Study Introduction Our client. used SQL Server 2005 as DW database for their products. o Sequential processing done by the SQL Server.

there were quite a few steps that were required for breaking down huge data into smaller subsets and then processing this data. These may need modifications so as to achieve optimum results.Database Migration Case Study Achievements  The Production cycle time was brought down from 6 hrs to 40 min. phenomenally. SQL Server scripts may not work as is on Netezza. The performance of the BI Reports increased (Report which ran for 2 mins on SQL Server now runs within 30 secs in Netezza) In the existing SQL Server Production cycle code. This improved the turnaround time of the teams which used these reports for analysis and QC. Syntactical errors in the code are also uncovered during procedure run time. This improved the performance of BI Reports for data quality testing which were run after the completion of the daily load in Production cycle. all these additional objects and processing were removed from the Production cycle code. scripts and SQLs need to be optimized differently for which there is Need for technical expertise for converting existing T-SQL and SQL Server scripts to Netezza NZSQL. Since Netezza is good at handling huge data and processing queries in parallel.   InfoCepts Case Study Page 3 of 3 . Compilation of Netezza code is not very strong. Debugging of Netezza code is difficult since Netezza error messages are not very detailed.   Constraints  Since Netezza appliance stores and handles data differently than traditional RDBMS like SQL server and Oracle.