Database Management Systems

Entity reuse is achieved through caching - when an entity is fetched from the database, it can be cached in memory and retrieved from the cache when needed on other pages. This avoids repeated database calls for the same data, improving performance. Calling the database again would defeat the purpose of reuse, and storing in in-memory tables is a different approach altogether.

By default, ASP.NET uses cookies to store the Session ID on the client's browser (the cookie is named ASP.NET_SessionId by default). While session data itself can be stored in memory, State Server, or SQL Server, the ID itself is transmitted via a cookie unless cookieless session state is explicitly enabled.

SQL Server supports four standard isolation levels: Read Uncommitted (no locking), Read Committed (default), Repeatable Read (locks held), and Serializable (highest isolation). These control how transactions handle concurrent data access.

Linked Servers in SQL Server allow users to execute commands against OLE DB data sources. They can be created to both SQL Server instances and non-SQL Server databases, including Oracle, MySQL, and Sybase, making the statement false.

The stsadm -o backup command in SharePoint locks the site during backup to ensure data consistency. Users cannot modify content while the backup is in progress, preventing incomplete or corrupted backups. The site becomes read-only temporarily, then automatically unlocks when backup completes.

The arschema table is the core database table in ARS that contains schema definitions for all forms. It stores form structure, field definitions, and metadata. The other options are variations of this name but incorrect - the actual table name is 'arschema' (all lowercase, one word).

ARS database requires Unicode support to handle multiple languages properly. If the database is not in Unicode character set, it cannot store or display characters from different languages correctly. Multi-language support depends on the database collation and character set being Unicode (UTF-8 equivalent).

A Source Qualifier in Informatica represents the rows that a Source transformation returns from a single source. It can only access data from one relational table or source definition. To join tables from different databases or servers, you need multiple Source Qualifiers followed by a Joiner transformation.

In Informatica PowerCenter, indexes and tables can be created or dropped at pre-session or post-session SQL commands at three levels: Source qualifier (before reading from source), Target (before writing to target), and Session (pre/post-session SQL). Workflow level doesn't have this SQL capability.

Warehouse Builder supports multiple CASE tools as source metadata suppliers, including all the versions listed: Sybase Power Designer 7.0, CA Erwin 3.0 to 3.5.2, and CA AllFusion ERwin Data Modeler 4.0 SP1 to 4.1.

In Oracle Warehouse Builder, a single Runtime Repository Schema can manage and serve multiple Target schemas. This design allows one repository to track metadata and execution history for multiple data warehouse targets. The one-many cardinality means one repository instance corresponds to many target schemas.

Oracle Warehouse Builder supports heterogeneous data sources for ETL operations. This includes Oracle databases (native support), flat files (CSV, delimited, fixed-length), and enterprise systems like SAP R/3 through specific connectors. This multi-source capability is a key feature for enterprise data integration.

Oracle Warehouse Builder (OWB) is capable of generating SQL and PL/SQL for Oracle databases, as well as ABAP code for extracting data from SAP systems. Since it can generate all these languages depending on the target and source systems, 'All of the Above' is the correct answer.

OWB integrates with Oracle's parallel DML capabilities to significantly boost data loading performance. By enabling parallel inserts, updates, and deletes, large-scale data transformations can process multiple data partitions simultaneously. This feature is essential for high-performance data warehouse operations.