Database Management Systems

The sql.bsq script creates the data dictionary base tables during database creation. This script contains the fundamental CREATE TABLE statements for dictionary objects. catalog.sql creates views, catproc.sql creates PL/SQL packages, and dictionary.sql is not a standard Oracle script.

IIS 6.0 stores its configuration in an XML file called 'metabase.xml' located in the %SystemRoot%\system32\inetsrv\ directory. Unlike earlier versions of IIS that used a binary metabase format, IIS 6.0 made the configuration human-readable and editable XML. This was a significant improvement for administration and backup/recovery. Note that IIS 7.0 and later moved to a different configuration system using .config XML files instead.

Android uses SQLite as its built-in database engine for storing structured data. SQLite is a lightweight, serverless database that requires minimal configuration and is ideal for mobile applications. Developers can use SQLiteOpenHelper to manage database creation and versioning.

In-memory deduplication uses a hash set to track seen records, operating in O(n) time with a single pass. Sort-based dedup requires O(n log n) for sorting plus a pass to remove duplicates. Rollup performs aggregation, not duplicate removal. With sufficient memory, in-memory is fastest.

Data migration testing validates both the transformation logic (data mapping rules between source and target) and the functional correctness of the application using migrated data. GUI testing ensures the application works correctly with the new data, while mapping rule verification confirms the ETL logic is accurate. Both aspects are essential for complete migration validation.

Entity Client is NOT an abstraction over ADO.NET Database provider model. Instead, it is part of the Entity Framework that provides an abstraction over the Entity Framework's conceptual model itself. Entity Client uses Entity SQL to query the conceptual model and works with the Entity Framework's layers rather than directly with ADO.NET database providers.

An .edmx file is an XML-based file that contains three sections: conceptual model (SSDL/CSDL definitions), storage model (database schema), and mapping specifications (MSL) between these models. Being an XML file allows it to be human-readable and editable while defining the complete Entity Data Model structure that Entity Framework uses.

When generating an Entity Data Model in Visual Studio, database connection details (connection string, provider information) are saved in the application's Configuration File (app.config or web.config). The EDMX file contains model and mapping definitions, while connection strings belong in configuration files for security and maintainability, allowing changes without recompilation.

The Conceptual Model is the implementation of the Entity Data Model (EDM) specific to Entity Framework. It represents an abstract specification for data structures, defining entities and relationships in the application domain independent of the underlying database storage. The conceptual model uses the CSDL (Conceptual Schema Definition Language) to define the entity-relationship representation.

EntityConnection is the class used to establish a connection to the conceptual model in Entity Framework. DbConnection is a generic base class, SQLConnection is SQL-specific, and ODBCConnection is for ODBC.

The correct namespace for Entity Framework's data provider is System.Data.EntityClient. This namespace contains classes for connecting to and executing commands against the Entity Framework. Option A incorrectly places 'Entity' before 'Data', while B and D are fabricated combinations that don't exist in the .NET Framework.

The Entity Data Model can include tables, views, and stored procedures - all of these database objects. Therefore 'All of these' (Option D) is correct. Each individual option (A, B, C) is technically correct but incomplete on its own.

The Entity Data Model (EDM) is the correct answer - it's a conceptual model for representing data as entities and relationships, abstracting the underlying storage structure. Option A (Enterprise Data Model) is not a standard term, Option C refers to object-oriented programming concepts, and Option D is not a recognized data model pattern.

MSDL stands for Mapping Schema Definition Language, which is a specification used to define XML schema mapping schemas within enterprise applications and data integration frameworks. The other options are simply incorrect or fictional variations of this database mapping acronym.