NPS (Netezza Performance Server) Database Administration

NPS allows a maximum of 4 columns for a distribution key. Distribution keys determine how data is spread across data slices and are crucial for query performance. Using up to 4 columns gives flexibility for multi-column distribution strategies. Fewer than 4 is allowed, but more is not supported.

The statement is False because NPS doesn't support this ALTER TABLE syntax. NPS has limited ALTER TABLE capabilities and doesn't allow adding columns with this syntax. In NPS, you typically need to recreate the table to add columns. The statement looks like SQL from other databases but doesn't work in NPS.

This is a duplicate of question 134914 testing the same concept. The statement is False because NPS doesn't support this ALTER TABLE syntax for adding columns. NPS has limited DDL support compared to standard SQL databases.

In Netezza (NPS), the standard SQL command to rename a table is ALTER TABLE customer RENAME TO customer_new. The syntax RENAME TABLE customer TO customer_new is invalid and will result in a syntax error, making the statement false.

Boolean data types have only 2 possible values (true/false), which creates severe data skew - all rows distribute to just 2 SPUs instead of spreading evenly across all available SPUs. Good distribution keys need high cardinality to ensure uniform data distribution.

In NPS architecture, the SMP (Symmetric Multiprocessing) host controls data distribution. Broadcasting means the SMP host sends copies of the entire table to all SPUs (Snippet Processing Units) so each SPU has the complete dataset for operations like joins or aggregations.

The semicolon is the standard SQL command terminator in nzsql (Netezza's SQL interface, similar to PostgreSQL). It signals to the SQL parser that the command is complete and ready for execution. Quotes are for string literals, not command termination.

In nzsql, \dpu (display permissions for users) shows user permissions. Other options serve different purposes: \du lists users (PostgreSQL-style), \dt lists tables, and \d describes database objects. Only \dpu specifically displays permission information.

The nzsql -d flag specifies which database to connect to (requires a database name as argument), it does not list databases. To list all databases in nzsql, use the \l command once inside an nzsql session, not the -d command-line flag.

In Netezza Performance Server (NPS), a table can be distributed on up to 4 columns when using multi-column distribution. Distributing on more than 4 columns is not supported by the query planner and database engine.

The NPS 10600 is a specific Netezza appliance model that contains 672 SPUs (Snippet Processing Units) as part of its hardware architecture. This is a factual specification for this particular NPS model.

The SQL syntax is incorrect for Netezza. The parentheses around the column definition are wrong. The correct syntax should be: ALTER TABLE customer ADD COLUMN newcol char(10); (no parentheses around column name and type).

Boolean data types have only 2 possible values, which creates severe data skew - all rows distribute to just 2 SPUs instead of spreading evenly. Good distribution keys require high cardinality to ensure uniform data distribution across all available SPUs.

The RENAME TABLE syntax is incorrect for Netezza. The proper syntax uses ALTER TABLE with RENAME TO clause: ALTER TABLE customer RENAME TO customer_new; Netezza does not support the RENAME TABLE statement shown.

The RENAME TABLE syntax is incorrect for Netezza SQL. The correct command uses ALTER TABLE with the RENAME TO clause: ALTER TABLE customer RENAME TO customer_new; The statement as written will not execute successfully.

The SQL syntax shown is incorrect. Netezza's ADD COLUMN syntax does not use parentheses around the column definition. The correct syntax is: ALTER TABLE customer ADD COLUMN newcol char(10); (without parentheses wrapping the column specification).

In Netezza Performance Server, disk space on each SPU is allocated in units called extents. The minimum extent size is 3 MB, which is the fundamental storage granularity - Netezza allocates space in 3 MB chunks even for smaller amounts of data.

In NPS (Netezza Performance Server), the nzsql \d command describes database objects like tables. The example correctly shows that \d customer will display the customer table's structure. This is standard psql/nzsql behavior for object introspection.

In nzsql (and PostgreSQL), the \du internal command lists all database users/roles defined in the system. This is correct - it's a standard meta-command for user management and inspection.