Database Management Systems

In Siebel's access control model, users with the same Responsibility can see different data on the same view due to visibility controls like organization-based access, position-based filtering, and access groups. View access is consistent across organizations for a given responsibility (B is false), visibility is not determined by Responsibility + ID + Position combination (C is wrong), and users with different access levels CAN view the same data if they have appropriate permissions (D is false).

JDBC stands for Java Database Connectivity and provides standard API access to relational databases, flat files, and spreadsheets. It does not natively bridge the object-relational mismatch (unlike ORM tools like Hibernate) or target XML databases directly.

Type 1 JDBC drivers, also known as the JDBC-ODBC bridge, translate JDBC API calls into ODBC driver calls, relying on native ODBC libraries on the client machine.

The DIKW hierarchy consists of Data, Information, Knowledge, and Wisdom. Tools can effectively store and manage data, information, and even knowledge through databases and knowledge management systems. However, wisdom represents the ability to apply knowledge judiciously in context - it's inherently human and cannot be captured by tools.

The DIKW (Data-Information-Knowledge-Wisdom) hierarchy represents how understanding develops progressively. Raw data becomes meaningful information, information is contextualized into knowledge, and knowledge is applied to gain wisdom for decision-making.

Oracle supports multiple table partitioning strategies: Range (by value ranges), List (by explicit value lists), Hash (for even distribution), and Composite (combining methods). Index partitioning is separate, and Rowid partitioning isn't a standard partitioning type.

sp_configure is the correct system stored procedure to view and modify SQL Server-level configuration parameters and properties. It displays or changes server configuration options. sp_helpserver shows server information, sp_helpdb is for database details, and sp_get_serverinfo doesn't exist.

sys.dm_db_index_physical_stats is the Dynamic Management View (DMV) specifically designed to return size and fragmentation information for indexes. It provides details like page count, average fragmentation percentage, and record count. sys.dm_os_schedulers is for OS schedulers, sys.dm_exec_requests shows executing requests, and sys.dm_db_index_usage_stats tracks index usage statistics.

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.

The acronym ACID stands for Atomicity, Consistency, Isolation, and Durability, which are the standard set of properties that guarantee reliable transaction processing in database systems.