Computer Knowledge
Database Management Systems
5,344 Questions
Database Management Systems (DBMS) form the core framework for data storage, retrieval, and security in modern software applications. Concepts such as the E-R model, backup planning, SQL integration, and big data architecture are essential for computer knowledge sections. This hub offers a comprehensive set of practice questions to master DBMS fundamentals and advanced database operations.
E-R Model ConceptsBackup and RecoverySQL Server UpgradesJDBC and ODBCBig Data CharacteristicsData VirtualizationOracle Database
Database Management Systems Questions
-
Programmers
-
Project Managers
-
Technical Writer
-
Database Administrators
D
Correct answer
Explanation
Database Administrators (DBAs) are responsible for designing database schemas, creating tables and indexes, implementing constraints, and managing the overall database structure to support application requirements. Programmers focus on code, technical writers on documentation, and project managers on coordination.
-
Attributes are stored against Characteristic in BI.
-
Attributes are part of Metadata
-
There are two types of Attributes Text and Navigation
-
Navigation Attributes provide functionality similar to characteristic in query definition.
-
A basic key figure of the InfoProvider whose values have been restricted by the use of a formula.
-
A basic key figure of the Infoprovider that has been restricted by one or more characteristic selections.
-
A basic key figure that is displayed in conjunction with a hierarchy.
-
None of the above
B
Correct answer
Explanation
A restricted key figure is a basic key figure filtered by one or more characteristic values (e.g., Revenue restricted to Country='USA'). It is NOT defined by formulas (A) - that would be a calculated key figure. Hierarchy display (C) is unrelated. B correctly captures the core concept.
-
Calculated Key Figures can be stored at Infoprovider level.
-
Calculated Key Figures can be stored in the PSA
-
Calculated Key Figures can be stored at Query level
-
Calculated Key Figures stored at Query level can be reused
A,C
Correct answer
Explanation
Calculated key figures can be defined at the InfoProvider level (A, reusable across queries) or locally within a specific query (C, query-specific). They are NOT stored in the PSA (B) - PSA is for transaction data storage. Query-level calculations are local to that query and cannot be reused elsewhere (D is false).
-
to make it look good
-
to increase performance
-
To comply with the multidimensional modelling rules
-
To avoid redundancy
D
Correct answer
Explanation
Normalization's primary purpose is eliminating data redundancy and ensuring each data element is stored in only one place (D). While it can improve data integrity, normalization often DECREASES performance (B is wrong) by requiring more joins. It's not about aesthetics (A) or multidimensional modeling rules (C) - it's a relational database concept.
B
Correct answer
Explanation
A field (B) is the smallest unit of data storage in a database, holding a single type of information (e.g., a field for Customer_ID stores only IDs). A record (C) is a collection of fields representing one entity. A report (A) presents data output. A file (D) is the storage container, not a structural element.
-
Char
-
Varchar(Max)
-
Int
-
Float
B
Correct answer
Explanation
During Sybase-to-SQL Server migrations, the Sybase text datatype is mapped to varchar(max) (or nvarchar(max) if Unicode is needed). Legacy datatypes like text are deprecated in modern SQL Server versions in favor of varchar(max).
-
CallableStatement
-
PreparedStatement
-
ResultSet
-
only a
-
a,b and c
-
a and b
E
Correct answer
Explanation
Without frameworks, developers use standard JDBC API classes like CallableStatement (for stored procedures), PreparedStatement (for precompiled SQL queries), and ResultSet (for handling database output). Searching for any of these keywords is key to finding database-connecting Java files.
-
CMS_InfoObjects
-
CMS_SystemObjects
-
CMS_AppObjects
-
None of the above
C
Correct answer
Explanation
CMS_AppObjects is the virtual table that contains information about universes in BusinessObjects. CMS_InfoObjects stores general object metadata, CMS_SystemObjects contains system-level objects, and CMS_AppObjects specifically holds application objects including universes. Universe metadata like connections, classes, and objects are queried here.
-
Over Partition By
-
Over Group By
-
Both
-
None
A
Correct answer
Explanation
T-SQL allows columns in GROUP BY that are not in the SELECT list, but PL/SQL prohibits this. The OVER clause with PARTITION BY provides similar functionality in PL/SQL by allowing window functions without the restrictive GROUP BY requirement.
-
COLUMN = NULL
-
COLUMN is NULL
-
COLUMN in (Null, 0)
-
None
B
Correct answer
Explanation
MSSQL follows ANSI SQL standard for NULL comparisons using 'IS NULL' syntax. The equality operator (=) cannot be used with NULL values because NULL represents an unknown value, not a specific value to compare.
A
Correct answer
Explanation
Sybase allows SELECT statements to include columns that are not in the GROUP BY clause and are not aggregated. This is a Sybase-specific behavior that differs from ANSI SQL standard and most other databases.
B
Correct answer
Explanation
Sybase supports implicit type conversion, allowing date columns to be compared with varchar values. The database engine will attempt to convert the varchar value to a date type for comparison purposes.
-
varchar
-
int
-
text
-
binary
-
Image
C,E
Correct answer
Explanation
SQL Server has deprecated the legacy 'text' and 'Image' data types in favor of varchar(max) and varbinary(max). While still functional for backward compatibility, they are not recommended for new development. Varchar, int, and binary are fully supported modern types.
-
A procedure that is very small
-
A procedure being invoked by another procedure
-
A procedure that is not used by application
-
System stored procedures
B
Correct answer
Explanation
A child stored procedure is a procedure that is called (invoked) by another stored procedure. This is a common design pattern for modularizing complex database logic into reusable components.