Database Management Systems

SQL Server Agent is a Windows service that depends on the SQL Server service to be running. It executes scheduled jobs, alerts, and automated tasks. The other services (Browser, Integration Services, Full-Text Search) can run independently or don't have the same dependency relationship.

SQL Server has exactly three recovery models: Simple (no log backups, minimal logging), Full (complete transaction logging, requires log backups), and Bulk-Logged (minimal logging for bulk operations, still point-in-time recovery). T-log is not a recovery model - it's shorthand for transaction log, which is a file, not a recovery model.

SQL Server's default TCP port is 1433 for the default instance. This is the well-known port used by SQL Server clients to connect. Port 1441 is incorrect (off by 8), 25 is SMTP, and 8000 is commonly used for web servers or alternate applications.

SQL Server supports three main replication types: Transactional replication (changes propagated immediately), Snapshot replication (periodic full data refresh), and Merge replication (bi-directional, allows autonomous changes). Mirroring is a high-availability technology, not a replication method.

Database Mail is the correct component for sending emails in SQL Server 2005 and later versions. SQL Mail was the older technology (SQL 2000 era) but required a MAPI client and was less reliable. Database Mail uses SMTP and is the recommended approach.

The @@version global variable returns complete version information including edition, product level (RTM, SP, CTP), and build number. The other options are either non-existent stored procedures or return server configuration rather than version details.

Business Objects maintains repository databases that store universe metadata, security, and audit information. Built-in audit databases track user activity, report usage, and system events for compliance and governance reporting. This is a core BO feature.

Business Objects is primarily an OLAP (Online Analytical Processing) tool designed for multidimensional analysis, interactive reporting, and ad-hoc querying of data warehouses. It is NOT an ETL tool (that's Data Integrator) and while it produces reports, 'Reporting tool' is too narrow - OLAP captures its analytical capabilities better.

TRAQCommon is the module that handles all database transactions including stored procedure calls and data mapping operations. This module provides a centralized data access layer, abstracting database interactions from the rest of the application and maintaining consistency in data operations.

The TRAQ project is built using C# as the programming language with SQL Server 2005 as the database backend. This technology stack was commonly used in mid-2000s enterprise applications, combining the object-oriented capabilities of C# with the robust data management of SQL Server 2005.

The SecurityDefinition table contains authorization information for all users in the system. This table stores user roles, permissions, and access rights, serving as the central repository for security and authorization data that determines what each user can access and perform within the application.

Partition tables allow a single logical table to be divided into physical segments that can be stored separately. This feature is commonly used in multi-tenant applications where different users' data needs to be isolated while maintaining a single table structure. Static tables store data without segmentation, in-memory cache tables optimize read performance, and hash tables use a different indexing mechanism altogether.

The TRAQ application implements error logging by writing error details to text files stored on the web server. This is a common logging approach that provides persistence without requiring database connectivity during error scenarios. While database logging offers better querying capabilities, file-based logging ensures errors are captured even when database connections fail. Option C suggests both methods are used, but the question specifically asks for the primary method.

SQL Server 2005 was the database version used in the TRAQ application. This version introduced significant features including database mirroring, snapshot isolation, and enhanced security features compared to SQL 2000. SQL Server 2008 came later with additional improvements, and SQL Server 2010 does not exist as a version (the progression was 2008, 2012, etc.).