Database Management Systems

Internal LOBs (Large Objects like CLOB, BLOB) are stored directly inside the database files, whereas external LOBs (BFILEs) reside in external operating system files pointed to by a database column.

When JDBC connection creation fails during WebLogic server startup, WebLogic logs this as an ERROR level message because it represents a critical failure that prevents the server from functioning properly. ERROR level indicates a serious problem that requires immediate attention. WARNING is for potential issues that don't stop operation. INFO is for informational messages. CRITICAL is not a standard WebLogic logging level (the levels are ERROR, WARNING, INFO, DEBUG, TRACE).

Garbage collection monitoring is done at the JVM level by starting with the -verbose:gc flag (or -XX:+PrintGCDetails in newer JVMs). This prints GC activity to stdout. The weblogic.Admin utility doesn't have a GC parameter, and examining logs shows results but doesn't actively monitor.

In production mode, WebLogic's default connection pool size is 25 connections. In development mode, the default is lower at 15 connections. Option A (15) is the development mode default, and -1 would mean unlimited which is not the default.

A report purge removes all the data rows that were fetched by running the query, while keeping the report structure intact. This allows you to clear the data without deleting the report definition, essentially resetting it to an empty state ready for refresh.

Query synchronization is a WebIntelligence feature available in XIR2 and XI 3.x, allowing data from multiple queries to be combined in a single report. Crystal Reports does not have this specific query sync capability.

An instance in Business Objects terminology refers to a specific scheduled run of a report, stored as a static snapshot at the scheduled time. The report definition itself is not an instance - instances are the results of scheduled executions.

Averages should be calculated at the report level where they can be dynamically computed based on current data filters and query context. Universe-level aggregation is less flexible and database-level aggregation doesn't adapt to report-level conditions.

SQL Server 2005 had multiple editions to serve different use cases. Developer Edition is for development/testing, Express is a free lightweight version, Enterprise is for large-scale mission-critical workloads, and Standard is for moderate-scale departmental applications. Integration Edition was not a SQL Server 2005 edition.

SQL Server 2005 is a comprehensive platform with four main service components. Database Engine is the core for data storage and processing, Analysis Services provides OLAP and data mining, Integration Services handles ETL operations, and Reporting Services enables report generation and delivery. Mobile Engine is not a SQL Server 2005 component.

SQL Server 2005 enhanced Business Intelligence through key capabilities. Data Migration via Integration Services (SSIS) enables ETL operations. Improved analytical capabilities come from Analysis Services (SSAS) with enhanced OLAP and data mining. Superior Integration properties refer to better integration with other applications and Office. A smaller data engine is not a BI feature.

SQL Server 7.0 Standard Edition can upgrade to SQL Server 2005 Standard Edition (same tier) and Enterprise Edition (upgrade path). Developer and Express editions are lateral moves or downgrades - Microsoft doesn't support direct in-place upgrades from Standard to these editions. You would need to migrate data instead.

SQL Server 2005 Notification Services is a platform for developing and deploying applications that generate and send notifications to subscribers. It's specifically designed for sending personalized messages to large audiences. Database Mirroring is for high availability, Integration Services is for ETL - neither handles messaging.

SQL Profiler is primarily a diagnostic and performance monitoring tool. It's used to detect slow-running queries by capturing trace events, and for troubleshooting database issues by analyzing query patterns, deadlocks, and performance bottlenecks. It doesn't configure services directly - that's done through Configuration Manager or Surface Area Configuration.

SQL Server 2005 provides sqlcmd (the successor to osql) for running T-SQL queries from the command prompt. DTUTIL is for SSIS packages, BCP is for bulk data import/export, and Object Explorer is a GUI component in SSMS. Since sqlcmd isn't listed, 'None of the above' is technically correct given the options.