Database Management Systems

SQL transformation in Informatica can operate in Script mode (executes SQL scripts) or Query mode (executes single queries). Bulk mode and Normal mode are not valid execution modes for SQL transformation.

Repository service manages metadata storage and retrieval. Integration service handles job execution and scheduling. Mappings cannot be created without repository service because metadata access is required. Option D contradicts this fundamental dependency.

Source Analyzer can import: relational objects (tables, views, synonyms), COBOL files, XML files, and data models. It cannot import flat files containing binary data - only text-based delimited or fixed-width files are supported for flat file sources.

SQL (Structured Query Language) is designed specifically for Relational Database Management Systems (RDBMS). The relational model, based on mathematical set theory, organizes data into tables with rows and columns, which SQL manipulates. SQL does not support Hierarchical or Network database models (these are older models), and File Management is a lower-level OS concept, not a data model.

SQL is a domain-specific language designed for managing and querying data in relational database management systems (RDBMS). It is not used for developing system programs (which requires languages like C/C++), nor is it limited to business applications only. SQL's primary purpose is data definition, manipulation, and control within relational databases.

JOIN is the SQL mechanism for combining rows from two or more tables based on a related column between them. Normalization is about organizing tables to reduce redundancy, indexing improves query performance, and sequences generate unique numbers - none of these combine table data. JOINS (INNER, LEFT, RIGHT, FULL) are the fundamental SQL operation for merging data from multiple tables.

SQL stands for Structured Query Language, used for retrieving (SELECT), updating (UPDATE, INSERT, DELETE), and defining (DDL) data in databases. Option A ('Structured database Language') and Option B ('Structured programming Language') are incorrect terms. Option C ('Structured Query Analyzer') is a tool, not the language. SQL is the standard database programming language for relational databases.

BusinessObjects Enterprise architecture uses a tiered model. Application tier handles web/desktop client interactions (launchpad, CMC). Intelligence tier contains the semantic layer (universes) and report generation engines. Processing tier executes background jobs and report processing. 'Datastore tier' is not a standard tier name in BO architecture.

The 'Database Records to Read When Previewing or Refreshing a Report' setting in Crystal Reports Page Server specifically limits the number of records returned during preview or refresh operations. This prevents users from accidentally running reports that return excessively large datasets, which could impact system performance and resources. The other options listed serve different purposes - SQL_MAX_ROWS is not a standard setting, Limit SQL Cursor Fetch Size affects batch fetching, and Preview Sample Data is a different feature.

The Crystal Reports Job Server is responsible for executing scheduled reports and notifying the Central Management Server (CMS) about the status of report instances. After a scheduled report completes successfully, the Job Server sends status updates to CMS to log the execution results and update instance status. The Page Server handles on-demand viewing, Output File Repository Server manages file storage, and Web Application Server handles web interface - none of these directly notify CMS about scheduled job completion.

To answer this question, the user needs to have a basic understanding of buffering techniques used in database management systems.

Full buffering is a buffering technique in which the entire table is read into the buffer pool. This technique is appropriate for tables that are small and static, as well as tables that are accessed frequently and require fast access times.

Now, let's go through each option and explain why it is right or wrong:

A. Transaction Tables: Transaction tables are large and frequently updated, so full buffering is not appropriate for them. Instead, partial buffering or no buffering may be more appropriate.

B. Small Static tables: Small static tables are ideal for full buffering, as they are easy to load into memory and can be accessed quickly.

C. Internal Tables: Internal tables are usually small and accessed frequently, so full buffering may be appropriate for them.

D. Tables with generic Keys: Whether or not full buffering is appropriate for tables with generic keys depends on the size and usage patterns of the table.

Therefore, the answer is:

The Answer is: B. Small Static tables