Database Management Systems

In Business Objects (BO), the Designer console is specifically used for creating Universes - the semantic layer that maps database structures to business terminology. Desktop Intelligence is for reporting, CMC is for administration, and Rich Client is for report viewing/creation.

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.).

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.