Database Management Systems

A view in SQL Server is a virtual table whose contents are defined by a query, serving as a logical view of a table. It does not physically store data, ruling out "Physical view", and is based on select queries rather than stored procedures.

SQL Server 2005 offers three main high availability solutions: failover clustering for server-level protection, database mirroring for database-level redundancy, and log shipping for disaster recovery. Data Guard and RAC are Oracle technologies, not SQL Server features.

SQL Server Enterprise Edition provides full high availability features, including asynchronous database mirroring with automatic failover using a witness server. Standard Edition only supports synchronous mirroring without a witness, while Workgroup and Express have very limited mirroring capabilities.

Database recovery follows three steps: Analysis phase determines what needs recovery, Redo phase replays committed transactions, and Undo phase reverses uncommitted transactions. This is ARIES-style recovery. The order is Analysis→Redo→Undo. Option D incorrectly says 'Recovery' as a step rather than 'Undo'.

Information is data that has been processed, organized, or structured to provide context and meaning to users. Raw data alone (option not listed) has no meaning. 'Process', 'software', and 'storage' are tools or actions, not the result. Information is the meaningful presentation of data.

Recovery scenarios in QTP follow a fixed sequence: first define the trigger event that detects the error, then specify recovery operations to fix it, and finally define post-recovery operations. This wizard structure ensures systematic error handling.

Base SAS provides core functionality for data manipulation, statistical analysis, and reporting. It excels at generating reports, performing mathematical computations, and analyzing data. Options B, C, and D describe specialized SAS products (SAS/ACCESS, SAS/AF, SAS/CONNECT) rather than Base SAS.

SAS/ACCESS provides interfaces to various database systems including DB2. It enables SAS to read from and write to external databases. Options A, B, and D describe other SAS products: SAS/CONNECT (remote communication), SAS/FSP (data entry), and none match 3D creation.

SAS/CONNECT is specifically designed to facilitate communication, data transfer, and remote library access between a client SAS session and remote SAS sessions across different platforms. Other options describe different SAS products like SAS/GRAPH or SAS/AF rather than the communication capabilities of SAS/CONNECT.

DYNAMIC access mode allows programmers to access records sequentially or randomly on the same file in COBOL. SEQUENTIAL and RANDOM modes limit record retrieval to their respective patterns only. Therefore, DYNAMIC is the correct choice because it is the only mode that permits both access methodologies.

TMF (Transaction Management Facility) provides comprehensive database integrity protection against failures at multiple levels: disk drives and controllers, disk processes and CPUs, application processes, and entire system failures. This multi-layer protection ensures transactional integrity and recovery capabilities across all potential failure points in the system.

TMF provides key features including consistency (ACID properties), fault-tolerant record handling, rollback capabilities for failed transactions, and locking mechanisms for concurrency control. All these features work together to ensure reliable transaction processing and database integrity in HP NonStop systems.

In COBOL file access modes, DYNAMIC access allows records to be accessed either sequentially (using READ NEXT) or randomly (using READ with KEY). SEQUENTIAL mode only permits sequential access. RANDOM mode only permits random access by key. DYNAMIC combines both capabilities, making it the correct answer when both access types are needed.

TMF (Transaction Management Facility) provides database integrity and protection against failures at multiple levels. It protects against disk drive and controller failures through mirroring, against disk process and CPU failures through process monitoring and recovery, and against application process and entire system failures through transaction logging and rollback capabilities. Therefore, it protects against all the listed failure types.

TMF provides multiple features for database integrity. Consistency ensures all related data updates are atomic. Fault Tolerant Records protect against data corruption. Roll Back allows undoing incomplete transactions. Locking prevents concurrent access conflicts. All these are core TMF capabilities, making 'All of the above' the correct answer.