Netezza Architecture


Netezza:
========
Netezza is rows base database using colummar compression
Hash algorithm is used

S-Blade / Snippet Processing Unit (SPU):
=======================================
Blade Server Card and Netezza DB Accelerator (FPGA)

1 Blade Server Card = 8 Core CPU (2 Intel Quad-Core)
1 Blade Server Card = 16 GB DRAM
1 Netezza DB Accelerator = 8 Core FPGA (4x Dual-Core)
1 Snipet Processing Unit = 8 Disks (responsible for)
1 Snipet Processing Unit = 8 Snippet Processor
1 Snippet Processer = 1 Core CPU, 1 Core FPGA and 2 GB DRAM
1 S-Blade = 6 sisks and 2 spare disks

Snippet Processing Array (SPA):
===============================
1 Storage Processing Array (SPA) = 4 Disk Encloures
1 Storage Processing Array (SPA) = 2 Spares Disks
1 Disk Encloures = 12 Disks
1 Disk = 1 TB SAS Drive
1 Disk = data on drive call data slice (table are splits across data slides
1 Disk = Devided into three partion - Primary, Mirror and Temp
Failed drive is automatically regenerated on a spare disk
Bed sector are automatically rewritten from the mirror to the new disk sector
1 SPA / Chassis = 2 SAS Switch

Disk Enclosures:
================
Slice of User Data, Swap and Mirror partitions, High speed data streaming

Hosts:
======
SQL Compiler, Query Plan, Optimize, Admin
Hart  Bit Signel, Linux-HA
Distributed Replicated Block Device mirrors hard disks, partitions, logical volumes between hosts
All files in /nz and /export/home/nz partitions are repliacted

S-Blades:
=========
Processor & Streaming DB logic, High Performance dabase engine,
Streaming joins, aggregations, sorts, etc

Snippet Processing:
===================
FPGA Core - Uncompress, Project, Restrict, Visibility,
CPU Core - Complex, Joins, Aggs, etc

FPGA:
=====
Field Programmable Gate Array - Design done by Verilog - VHDL language
Xilinx chip from Xilinx the market leader
Used in high performance computing

Network Connectivity:
=====================
Migrate data upto 2 TB/hours
High speed network frabic
IP base prorocol which fully utilized

S-Blade Failover:
=================
Drives are automatically reassigned to active S-Blades
read-only queries are automatcically restarted
insert and update transaction are rollback
Load are automatically restarted from last successful checkpoint


TwinFin-12:
===========
4 Racks - 96 Hard Disks - 8 Disk Enclosures
96 1TB SAS Drives (4 hot spares)
2 Hosts (1 Active-1 Passive) - 8 Core CPU(2 Quad-Core Intel) 24 GB RAM
12 S-Blades and Two Racks / Chassis
1 Racks / Chassis = SPA (Storage Process Array)
144 TB/hr - 4 time compression
4 PDU (2 are Hosts and S-Blades and 2 are Storage Array)
8 JBOD chassis



Nettaza Users:
* All users are member of group PUBLIC (allow system view and allow user database access)
* Admin is database super user and has full access to all system functions and objects
* User name can be 128 char in length and store in uppercase
* Users, groups and database names must of Unique
* list a users permission \dpu
* create using nzsql or nzadmin GUI
* The nz user is the default Netezza system Administration account


Comments

Post a Comment

Popular posts from this blog

SSRS Report Design: Best Practices

Introduction Microsoft® SQL Server™ Reporting Services is a comprehensive reporting tool. In using Reporting Services, you can design and deliver a wide range of reports, from simple tables to online free-form reports with graphical items and interactive links. Reporting Services can render reports for a variety of client-viewing formats, including HTML, PDF, Excel, and image formats. The wide variety of options and choices can be problematic for report authors who must make numerous decisions when choosing how to lay out a report. This paper provides a few guidelines to make these decisions easier and answers common questions.
Read more

SSAS OLAP Design - Best Practices

Introduction This paper outlines the recommended best practices for designing OLAP databases in Microsoft SQL Server 2005 Analysis Services to better meet the functional and performance needs of users. Designing a database for Online Analytical Processing (OLAP) databases is very different from designing a database for Online Transaction Processing (OLTP) and requires a different approach for achieving optimal results. The best practices recommendations are grouped into the following sections: Data Source Design Best Practices Dimension Design Best Practices Cube Design Best Practices Partition Design Best Practices Aggregation Design Best Practices Within each section, these best practices are ordered roughly by priority, where priority is a combination of how important the best practice is and how often you must worry about it. Major topics not covered include best practices for the design of calculations and for server management and operations.  These two topics are s...
Read more

Enable Usage-Based Optimization in SSAS

Usage-Based Optimization is a fantastic feature in SSAS to improve the most frequently used MDX queries of any cube database. This feature is used to design aggregations based on actual user queries using Business Intelligence Development Studio. But when ever you try to design  Usage-Based Optimization  you might have seen all the options  disabled.  This uses the technique of creating aggregations on FREQUENTLY USED queries in the given time interval.  We can enable the options in Usage-Based Optimization wizard. Connect to SSAS using SSMS (Sql Server Management Studio). Right click on the server and select properties as shown below. set CreateQueryLogTable to  true. Set the value of  QueryLogConnectionString  to any database where you wish to store your queries. Set the value of  QueryLogSampling  to the appropriate value for your environment (the default value of 10 means every 10th query will be logged). The lowe...
Read more