Tags » Netezza

UDX (User Defined Extensions)

Introduction to UDX:

Traditionally we support three in-built functions to perform basic in-house database functionalities. i.e. Scalar functions, Aggregate functions, Table functions.

Additionally, Netezza provides a user to implement a freestanding, executable data-processing program that runs “out of process,” and register it in a database. 295 more words

Information Management

Netezza: dbos.log (vs) pg.log

Both – dbos.log and pg.log – these logs are very useful in understanding SQL statements that are hitting Netezza database system.

dbos.log: Records information about SQL plans (/nz/kit/log/dbos/dbos.log) 235 more words


Netezza: Multiple history databases

(Q) Can we have multiple history databases created?

An history database captures information about user activity such as


Netezza Tip: Groom Rows from Uncommitted Transactions

I have a series of joins that insert a large number of rows into a table. As you can imagine, I want this process to perform as well as it can, and in Netezza that means finding the best distribution and utilizing zone maps where possible. 377 more words


netezza?teradata? ?now hadoop ?

As I sit browsing through.. I found a good piece for info showcasing the importance of hadoop .. our tiny elephant.. and how it’s different from the mighty Teradata or Netezza.. 481 more words

Information Management

Zone Maps: Netezza's Answer to Indexes in Big Data

There are no indexes in Netezza. This is an intentional design choice. Indexes are effective in an OLTP system, where transactions affect a single row or two, but not in an OLAP system, where transactions affect large sets of data. 1,660 more words