FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W64675093> ?p ?o ?g. }

• W64675093 endingPage "386" @default.
• W64675093 startingPage "385" @default.
• W64675093 abstract "IBM Netezza is a powerful and highly parallelized Data Warehousing system that is simple to administer and to maintain. This system is an appliance that is purpose-built for data warehousing. The system is commonly referred to as data warehouse appliance that is designed specifically for running complex data warehousing workloads. The concept of an appliance is realized by integrating the database, server and the storage into an easy to deploy and manage system.In any database system the main bottle neck is IO. IBM Netezza reduces this bottleneck by using a commodity FPGA (Field-Programmable Gate Array) by pushing the SQL closer to silicon to help improve IO performance. This core component of the appliance is referred to as the Database Accelerator.The Database Accelerator along with the other components of the IBM Netezza appliance was discussed during a short high-level overview of the architecture. This overview was presented at the beginning of the workshop during a brief presentation. The presentation also included the basic usage on how to administer and maintain a Netezza database. The concepts covered in the presentation were reinforced by getting hands on experience using a Netezza appliance. Instead of using an actual IBM Netezza appliance a virtualized environment was provided with a lab manual outlining the steps and commands to run. The lab manual also included explanations for each of the step-by-step instructions used in the exercises.The agenda for the topics covered in the Hands-on-Lab exercises was:1. Create Netezza Database Users and Groups (and set privileges)2. Create the Workshop database3. Create tables in the Workshop database4. Load data into the Netezza Appliance with the nzload utility using the External Table framework5. Examine the concept of Data Distribution to choose an appropriate Hash Key6. Maintain a Netezza database using the groom commandThe workshop showed how simple it was to setup a IBM Netezza appliance after it has been delivered and configured. A factory-configured and installed IBM Netezza appliance includes some of the following components:• An IBM Netezza data warehouse appliance with pre-installed IBM Netezza software• A preconfigured Linux operating system (with Netezza modifications)• Several preconfigured Linux users and groups:c The nz user is the default Netezza system Administration accountc The group is the default group• An IBM Netezza database user named ADMIN. The ADMIN user is the database super-user, and has full access to all system functions and objects• A preconfigured database group named PUBLIC. All database users are automatically placed in the group PUBLIC and therefore inherit all of its privilegesThe IBM Netezza appliance also includes a SQL dialect called Netezza Structured Query Language (NZSQL). You can use SQL commands to create and manage your Netezza databases, user access, and permissions for the databases, as well as to query and modify the contents of the databases.On a new IBM Netezza appliance, there is one main database, SYSTEM, and a database template, MASTER_DB. IBM Netezza uses the MASTER_DB as a template for all other user databases that are created on the system.Before creating the databases and tables, a brief explanation was provided about the virtualized environment used in the workshop. This also included how to connect to the Netezza appliance, which is completed through the Netezza SMP Host. Once connected to the Netezza appliance a set of new users were created, which were used for the remainder of the workshop. The concept of users and privileges were explored later when the database and tables were created. This would involve setting up a basic Security Access Model, which restricted or permitted certain actions to objects within the Netezza Appliance.After the Netezza Database Users were created the database and the tables for the workshop were created. Once the database and the tables are created, the next step as with any data warehouse environment is to load data into the tables in the database. This was easy by using the Netezza utility nzload which uses the External Table framework to efficiently load data in to a Netezza database. This framework contains more than one component, some of these components are:• External Tables -- These are tables stored as flat files on the host or client systems and registered like tables in the Netezza catalog. They can be used to load data into the Netezza appliance or unload data to the file system.• nzload -- This is a wrapper command line tool around external tables that provides an easy method loading data into the Netezza appliance.• Format Options -- These are options for formatting the data load to and from external tables.With a good understanding on how to create and populate tables in a Netezza database discussion followed on the importance of Data Distribution. Since IBM Netezza is built on a massively parallel architecture that distributes data and workloads over a large number of processing and data nodes, the single most important tuning factor is choosing the right distribution key. The distribution key governs which data rows of a table are distributed to a data slice and it is very important to choose an optimal distribution key to avoid data skew, processing skew and to make joins co-located whenever possible. This concept was so important that a separate section was devoted to this topic. The exercises examined how to pick the best Hash Key for distribution for each of the tables created in this workshop. During these set of exercises CTAS tables were utilized that showed how easy it is to change the Hash Key for a table without having to manually recreate and reload the data in the table.Before finishing the exercises for the day, one more important utility is explored to show how simple it is to maintain tables in a Netezza database. This utility was the GROOM command, which is used to reclaim free-space in a table. The concept of free-space in a Netezza database was illustrated by discussing how transactions are handled in a Netezza database. This included how SQL INSERTs, DELETEs, and UPDATEs are handled in a Netezza database.After learning these concepts, which were reinforced by the hands-on exercises provided in the workshop, you can now get an IBM Netezza Warehouse Appliance up-and-running after the appliance has been delivered and configured before being handed over to you." @default.
• W64675093 created "2016-06-24" @default.
• W64675093 creator A5078947386 @default.
• W64675093 creator A5091738310 @default.
• W64675093 date "2011-11-07" @default.
• W64675093 modified "2023-09-24" @default.
• W64675093 title "Introduction to the IBM Netezza warehouse appliance" @default.
• W64675093 hasPublicationYear "2011" @default.
• W64675093 type Work @default.
• W64675093 sameAs 64675093 @default.
• W64675093 citedByCount "9" @default.
• W64675093 countsByYear W646750932016 @default.
• W64675093 countsByYear W646750932019 @default.
• W64675093 countsByYear W646750932020 @default.
• W64675093 countsByYear W646750932021 @default.
• W64675093 crossrefType "proceedings-article" @default.
• W64675093 hasAuthorship W64675093A5078947386 @default.
• W64675093 hasAuthorship W64675093A5091738310 @default.
• W64675093 hasConcept C111919701 @default.
• W64675093 hasConcept C135572916 @default.
• W64675093 hasConcept C144133560 @default.
• W64675093 hasConcept C162853370 @default.
• W64675093 hasConcept C171250308 @default.
• W64675093 hasConcept C192562407 @default.
• W64675093 hasConcept C41008148 @default.
• W64675093 hasConcept C50416739 @default.
• W64675093 hasConcept C70388272 @default.
• W64675093 hasConcept C77088390 @default.
• W64675093 hasConceptScore W64675093C111919701 @default.
• W64675093 hasConceptScore W64675093C135572916 @default.
• W64675093 hasConceptScore W64675093C144133560 @default.
• W64675093 hasConceptScore W64675093C162853370 @default.
• W64675093 hasConceptScore W64675093C171250308 @default.
• W64675093 hasConceptScore W64675093C192562407 @default.
• W64675093 hasConceptScore W64675093C41008148 @default.
• W64675093 hasConceptScore W64675093C50416739 @default.
• W64675093 hasConceptScore W64675093C70388272 @default.
• W64675093 hasConceptScore W64675093C77088390 @default.
• W64675093 hasLocation W646750931 @default.
• W64675093 hasOpenAccess W64675093 @default.
• W64675093 hasPrimaryLocation W646750931 @default.
• W64675093 hasRelatedWork W1461360349 @default.
• W64675093 hasRelatedWork W1474183241 @default.
• W64675093 hasRelatedWork W157207381 @default.
• W64675093 hasRelatedWork W1969877208 @default.
• W64675093 hasRelatedWork W2004376136 @default.
• W64675093 hasRelatedWork W2098730617 @default.
• W64675093 hasRelatedWork W2133156997 @default.
• W64675093 hasRelatedWork W2144005171 @default.
• W64675093 hasRelatedWork W2286264920 @default.
• W64675093 hasRelatedWork W1011211348 @default.
• W64675093 hasRelatedWork W1035620120 @default.
• W64675093 hasRelatedWork W107517586 @default.
• W64675093 hasRelatedWork W129613189 @default.
• W64675093 hasRelatedWork W1488741672 @default.
• W64675093 hasRelatedWork W1502553295 @default.
• W64675093 hasRelatedWork W248498392 @default.
• W64675093 hasRelatedWork W583582720 @default.
• W64675093 hasRelatedWork W955697677 @default.
• W64675093 hasRelatedWork W985174804 @default.
• W64675093 hasRelatedWork W986189469 @default.
• W64675093 isParatext "false" @default.
• W64675093 isRetracted "false" @default.
• W64675093 magId "64675093" @default.
• W64675093 workType "article" @default.