If you're looking for Netezza Interview Questions for Experienced or Freshers, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research, Netezza has a market share of about 3.7%. So, You still have the opportunity to move ahead in your career in Netezza Analytics. Mindmajix offers Advanced Netezza Interview Questions 2021 that helps you in cracking your interview & acquire a dream career as Netezza Analyst.
Netezza Interview Questions
Q. What are the data warehouse appliances you know?
- Oracle Exadata
Q. What are the environment variables that are required to connect to Netezza?
Ans: The environment variables required are: NZ_HOST, NZ_DATABASE, NZ_USER, NZ_PASSWORD
Q. What are the different states of Netezza?
- Online: Normal or usual state.
- Stopped: Netezza will shut down after completing current queries, no new queries allowed.
- Offline: Waits for completion of current queries, new queries in queue receives an error.
- Paused: Same as above, but no error displayed. Typically caused during Netezza boot up or startup.
- Down: Just plain down, could be due to the Netezza server problem or user-initiated.
Q. What are the constraints on a table that are enforced?
Ans: The only constraint Netezza supports is Not null. There are no primary key and foreign key constraints in Netezza.
Q. Can you insert duplicate rows in the Netezza table?
Ans: Yes. As there are no primary key constraints in Netezza you can insert duplicate rows.
Q. How the NOT NULL specification on a column improves the Netezza performance?
Ans: Specifying Not Null on each column in the table results in better performance. Netezza tracks the NULL values at row header level. Having NULL values results in storing references to NULL values in the header. If all columns are NOT NULL, then there is no record header.
Q. How FPGA can be helpful in improving query performance?
Ans: While reading data from the disk, the Field Programmable Gate Array (FPGA) on each SPU filters out unwanted data. This process of data elimination removes IO bottlenecks and frees up downstream components such as the CPU, memory, and network from processing extra data.
Q. What is a snippet?
Ans: A snippet is a small unit of work that is carried out in SPU.
Q. What are zone maps?
Ans: An extent is the smallest unit of disk allocation on an SPU. Zone maps is internal mapping structures to the extents that take advantage of the internal ordering of data to eliminate extents that do not need to be scanned. Zone maps transparently avoid scanning of unreferenced rows. Zone maps are created for every column in the table and contain the minimum and maximum values for every extent.
Q. How the zone maps are created and updated?
Ans:Zonemaps are created and refreshed for every SPU when you Generate statistics, Nzload operation, Insert, update operations, Nzreclaim operation.
Q. What is generate statistics and generate express statistics OR what is the difference between generate statistics and generate express statistics?
- Generate statistics is used to gather statistics about each table column’s proportion of duplicate values, minimum values, maximum values, null values, unique values, and updates the system catalog tables.
- The difference between ‘generate statistics’ and ‘generate express statistics’ is based on how the column uniqueness is calculated. The ‘generate express statistics’ calculates estimated dispersion values based on the sampling of rows in the table. ‘Generate express statistics’ uses approximation in generating the stats whereas ‘generate statistics’ uses all the rows in the table.
Q. What is the use of creating materialized views?
Ans: A materialized view reduces the width (number of columns) of data being scanned in the base table by creating a thin version (fewer columns) of the base table that contains a small subset of frequently queried columns.
Q. What is the distribution of materialized views?
Ans: A materialized view has the same distribution key as the base table.
Q. What are the limitations of materialized views?
- You cannot insert, update, delete, or truncate a materialized view. Any changes on the base tables will reflect into materialized views.
- You can specify only one base table in the from clause.
- The base table can’t be an external table, a system table, or a temporary table.
- You cannot use a where clause in the materialized view.
- Expressions are not allowed as columns.
Q. What are the best practices of creating materialized views?
- Create materialized views with few columns which are frequently queried.
- Specify order by clause on the most restrictive columns (columns used in where clause).
- Periodically or manually refresh the materialized views.
Q. What are the partitioning methods available in Netezza?
Ans: There are two partitioning methods available in Netezza:
- Random partitioning: Distributes the data randomly.
- Hash Partitioning: Distributes the data on the specified columns.
Q. Up to how many columns you can specify in distribute on clause?
Ans: You can specify up to four columns in the distribution clause.
Q. If you did not specify any distribution on clause while creating a table, what distribution Netezza uses?
Ans: Netezza distributes the data on the first column and it uses Hash partitioning
Subscribe to our youtube channel to get new updates..!
Q. Can you update the columns used in the distribution clause?
Ans: No, the column that is used in the distribution clause cannot be used for updates.
Q. What data types are most suited for the columns specified in the distribution clause?
Q. How do you redistribute a table?
Ans: Use Create Table As (CTAS) to redistribute the data in a table. While creating the new table specify the distribution on clause to distribute the data on the new columns.
Q. If you did not specify any distribution clause, how the Create Table AS (CTAS) will distribute the rows?
Ans: CTAS will get a distribution from the original table.
Q. How do you check the rows in a table are equally distributed in all SPU’s or not?
Ans: To check the distribution of rows run the following query
SELECT data sliced, COUNT(*)FROM GROUP BY data sliced
Q. What is collocated join?
Ans: When you join tables that are distributed on the same key and used these key columns in the join condition, then each SPU in Netezza works 100% independent of the other, as the required data is available in itself. This type of joins is called collocated joins.
Q. When Netezza redistributes a table and when it broadcasts a table?
Ans: Whenever it is not possible to do a collocated join, Netezza either redistribute the tables or broadcasts the table. When the table is a small one, then Netezza broadcasts the table. Otherwise, Netezza redistributes the table.
Q. How do you remove logically deleted records?
Ans: Whenever you delete a row in a table, it is not physically deleted. It is logically deleted by flagging the deleted field in the table. NZRECLAIM utility is used to remove the logically deleted records.
Q. What is nzload?
Ans: Nzload utility is used to load data from a file into a table. It is used to load bulk data quickly and simultaneously rejects erroneous content.
Q. What are the ways to load data from a table into a file?
- Create an external table.
- Use NoSQL utility with -o option.
Q. What are the different ways to load data from a file into a table?
- Use nzload to load the data from a file into a table
- Create an external table and then load the original table using the external table.
Q. How Netezza updates a row in a table?
Ans: Netezza logically deletes the original row by flagging the deleted column with the current transaction id and inserts a new row with the updated values.
Q. Which two characteristics describe the materialized view. (Choose two.)
A. Materialized views can contain aggregates.
B. Materialized views can contain a HAVING clause.
C. Materialized views can contain a WHERE clause.
D. Materialized views can contain an ORDER BY clause.
E. Materialized views can reference only one base table in the FROM clause.
Ans: D, E
Related Article:IBM Netezza DBA
Q. Which CREATE DATABASE attributes are required?
A. The database name.
B. The database name and the redo log file name.
C. The database name and the tablespace name.
D. The database name and the temporary tablespace name.
Q. Which statement is true for database users and groups.?
A. All users must belong to the admin group.
B. Creation of users and groups is not allowed.
C. Users and groups are local and tied to a particular database.
D. Users and groups are global and not tied to a particular database.
Q. What is the maximum number of columns you can choose as organizing keys for a clustered base table?
Q. What should be considered when you are asked to select the distribution key columns for a very large fact table?
A. As many columns as possible.
B. Columns that contain many nulls.
C. Columns contain few unique values.
D. Columns used to join to other large tables.
Q. What is the command to display/monitor the status of a reclaim?
A. NZ stats -type reclaim
B. nzinventory -type regentasks
C. nzstate -type reclaim
D. nzinventory -type reclaim
Q. Which log file captures SQL submitted to the NPS system?
Q. Which one of the following pieces of information is maintained by Statistics on a table?
A. Table definition and structure
B. Min and Max value of columns
C. Table Object id
D. Access information
Q. Which one of the following pieces of information is maintained in the zone map table to assist the performance of a query?
A. Table definition and structure for each column
B. Table object id stored in the catalog
C. Min and Max value of a column to an extent.
D. Number for rows in a table
Q. Which system table could be used to find an object id for any table/view or object in a database?
Q. Explain FPGA and how is it useful for query performance.
Ans:FPGA: Field Programmable Gate Array (FPGA) is located on each SPU. Netezza is different from other architectures. Netezza can do a “hardware upgrade” through software by using FPGA. Hardware is reconfigured during install.
While reading data from disk, FPGA on each SPU also helps in ‘filtering’ unnecessary data before getting loaded into memory on each SPU. This way, FPGA does not overwhelm with all the data from the disk.
Q. What is a zone map.
Ans:Zone map in Netezza is similar (concept wise) to partitions in Oracle. Netezza maintains a map for data so that it does rely on a zone map to pull only the range it is interested in. For example, if we need to pull out data from Jan 2009 till June 2009 from a table that is distributed on the date column, the zone map helps us to achieve this. The zone map is maintained by Netezza automatically, no user intervention needed. Zone mapping is done at a block (extent) level. Netezza has zone maps for all columns (not just distributed column) and includes information such as minimum, the maximum, total number of records.
Q. How do you deal with historical data, with respect to zone maps.
Ans: Sort data first, based on historical data (for example, date), and load this in using nzload.
Q. What are different ways to load
- External tables
- Create table AS (aka, CTAS).
- Inserts (Eeeewee!!)
Q. Does everything gets cached in Netezza (or any other data appliance).
Ans: Typically only schema and other database objects are cached in appliances. Data is not cached, in general. In most cases, data is not saved anywhere (in any cache or on the host computer) and is streamed directly from SPU to client software.
Q. What is the best data appliance.
Ans: Obviously, it all depends. This is my (limited) view:
- From features respect, Green Plum.
- Popularity with a bit of hype, Netezza.
- Matured and well respected, Teradata.
- With existing database integration, Dataupia.
* Teradata: 72 nodes (two quad-core CPUs, 32GB RAM,104 / 300GB disks per node) and manages 2.4PB.
* Greenplum: Fox Interactive Media using a 40-node, Sun X4500 with two dual-core CPUs, 48 / 500GB disks, and 16 GB RAM (1PB total disk space)
Source: Vertica’s Michael Stonebraker!
Q. How is load achieved in Netezza and why is that quick/fast.
Ans: Loads bypass a few steps that typically a query would go through (a query goes through plan generation, optimization, and transaction management). Loads are done in terms of “sets” and this set is based on underlying table structure (thus loads for two different tables are different as their sets are based on table structures). Data is processed to check the format and distribution of records calculated very quickly (in one step), fills into the ‘set’ structure, and writes to the storage structure. Storage also performs space availability and other admin tasks, all these operations go pretty quick (think of them as UNIX named pipes that streams data and SPU stores these records).
Q. When are we likely to receive incorrect (aggregate) results.
Ans: Very rarely a driver may return aggregated results that are still getting processed back to the client. In this case, the client may assume that the calculation is complete, instead of updating with the latest or final results. Obviously, the driver has to wait for Netezza to complete operation on the host computer, before delivering results.
Q. Explain how data gets stored in Netezza and how does SPU failover takes place.
Ans: Data is stored based on a selected field(s) that are used for distribution.
==Data (A)==> Hash Function (B) ==> Logical SPU identifier list (C) ==> Physical SPU list (D) ==> Storage (E)
When data arrives, it is hashed based on the field(s) and a hash function (B) is used for this purpose. For example, for a hypothetical 32 node system, the logical SPU identifier list has 32 unique entries. If there are 1000 hashed data items from (B), there are 1000 entries in (C), all having only 32 SPU entries (a number of data items go to the same SPU, thus multiple (B) entries map to same (C)). For instance, (C) has values [3,19,30,7,20,25,11,3,22,19….]. This way, 1000 data entries are mapped. (D) has a physical IP address of both primary and failover SPU. If there is a failover, this is the only place where Netezza needs to update its entries. The same goes for a system that has a new SPU added. It is a little complicated, in principle, this is the concept.
Q. What are 4 environment variables that are required. What are the different states on Netezza?
Ans: Environment variables: NZ_HOST, NZ_DATABASE, NZ_USER and NZ_PASSWORD
* Online: Normal or usual state.
* Stopped: Netezza will shutdown after completing current queries, no new queries allowed.
* Offline: Waits for completion of current queries, new or queries in queue receive an error.
* Paused: Same as above, but no error displayed. Typically caused during Netezza bootup or startup.
* Down: Just plain down, could be due to Netezza server problem or user-initiated.
Q. Does Netezza support the concurrent update of the same record
Ans: In case of conflict in which the same record is set for modification, Netezza rolls back a recent transaction that is attempted on the same record, in fact, the same table. This is generally acceptable in DW environments. Netezza does support serialization transactions and does not permit dirty reads.
Q. How Netezza updates records. Give an idea of how transactions are maintained and how to read consistency is maintained.
Ans: Netezza does not update records in place, it marks records with a delete flag. In fact, each record contains two slots, one for create Xid another for delete xid. Delete xid allows us to mark a record with a current transactions for deletion, up to 31 transactions are allowed in Netezza for all tables. As noted earlier, only one update at a time allowed on the same table though. Here update refers to transactions that are not committed yet. Coming back to delete xid, this is how Netezza maintains transaction rollback and recovery. Once a record is modified, it’s delete xid is given transaction id; this is changed from the previous value of 0, all records when loaded will contain 0 for delete xid. Note that FPGA uses its intelligence to scan data before delivering them to host or applications.
[ROW id][Create xid][Delete xid]
[R1][T1] // First time a record is loaded, record R1
// After some time, updating the same record
[R1][T1][T33] // Record R1 is updated; note T33
[R33][T33] // New update record R33; similar to a new record this has zero for Delete Xid
If the record is deleted, simply deletion xid will contain that transaction id.
- Based on the above, how do you know a record is the latest. It has zero in delete xid flag.
- Extending the same logic, how do we know a record is deleted. It has non zero value in the delete xid flag.
- How do you roll back to the transaction? Follow similar to the above listing, we can roll back a transaction of our interest.
- Note that the transaction id is located in the create xid flag and that is our point of interest in this case. From what I know, row id and create id is never modified by Netezza.
Q. What happens to records that are loaded during nzload process, but were not committed.
Ans: They are logically deleted and the administrator can run nzreclaim, we may also truncate the table.
Q. Can a group become a member of another group in Netezza user administration. Can we use the same group name for databases?
Ans: In Netezza, a public group is created automatically and everyone is a member of this group by default. We can create as many groups and any user can be a member of any group(s). Group can not be a member of another group. Group names, user names, and database names are unique. That is, we can not have a database called sales and a group also called sales.
Q. How can we give global permission to user joe so that he can create a table in any database.
Ans: Login into system database and give that permission to the user by saying “grant create a table to joe;”
Q. What permission will you give to connect to a database.
Ans: List. Grant list, select on the table to the public (if logged into sales database, this allows all users to query tables in sales database).
Q. Do we need to drop all tables and objects in that database, before dropping a database.
Ans: No, the drop database will take care of it.
Q. What constraints on a table are enforced.
Ans:Not null and default. Netezza does not apply to PK and FK.
Q. Why NOT NULL specification is better in Netezza.
Ans: Specifying not null results in better performance as NULL values are tracked at row header level. Having NULL values results in storing references to NULL values in the header. If all columns are NOT NULL, then there is no record header.
Q. Create Table AS (CTAS), does it distribute data randomly or based on the table on which it received data.
Ans:Response: Newly created table from CTAS gets distribution from the original table.
Q. Why do you prefer to truncate instead of drop table command.
Ans: Just empties data from the table, keeping table structure, and permission intact.
Q. When no distribution clause is used while creating a table, what distribution is used by Netezza.
Ans: First column (same as in Teradata).
Q. Can we update all columns in a Netezza table.
Ans: No, the column that is used in the distribution clause cannot be used for updates. Remember, up to four columns can be used for the distribution of data on SPU. From a practical sense, updating distribution columns result in the redistribution of data; the single most performance hit when a large table is involved. This restriction makes sense.
Q. What data type works best for zone maps.
Ans: Zone maps work best for integer data types.
Q. What feature in Netezza you do not like.
Ans: Of course, a large list, especially when compared to Oracle. PK and FK enforcement is a big drawback though this is typically enforced at ETL or ELT process [ELT: Extract, Transform, and Load. Note that ‘Transform’ and ‘Load’ can happen within Netezza].