Q1
True / FalseIn Microsoft SQL Server, the CREATE TABLE statement can include a PRIMARY KEY constraint to enforce uniqueness and non-nullability on specified columns.
A PRIMARY KEY constraint in SQL Server ensures that the specified columns contain unique and non-null values.
Q2
True / FalseIn SQL Server, you cannot define a PRIMARY KEY constraint on a table during its creation using the CREATE TABLE statement.
A PRIMARY KEY constraint can be defined during table creation using the CREATE TABLE statement in SQL Server.
Q3
True / FalseThe CREATE TABLE statement in SQL Server allows defining default values for columns, ensuring that a specified value is used if no value is provided during insertion.
Default values can be specified for columns in SQL Server using the CREATE TABLE statement.
Q4
True / FalseIn SQL Server, the CREATE TABLE statement cannot be used to define foreign key constraints.
The CREATE TABLE statement in SQL Server can include foreign key constraints to enforce referential integrity between tables.
Q5
True / FalseThe CREATE TABLE statement in SQL Server can specify both column-level and table-level constraints, such as UNIQUE, PRIMARY KEY, and CHECK constraints.
SQL Server allows specifying column-level and table-level constraints in the CREATE TABLE statement to enforce data integrity rules.
Q6
True / FalseIn SQL Server, you can create a table with the CREATE TABLE statement that references tables in an ORACLE database using a linked server.
SQL Server supports linked servers to reference tables in other databases, including ORACLE, during table creation.
Q7
True / FalseThe CREATE TABLE statement in SQL Server allows for the creation of computed columns, which are virtual columns defined by an expression.
Computed columns can be defined in SQL Server using the CREATE TABLE statement, where their values are derived from an expression.
Q8
True / FalseIn SQL Server, a table created with the CREATE TABLE statement can only have one PRIMARY KEY constraint.
A table in SQL Server can have only one PRIMARY KEY constraint, which can consist of one or more columns (composite key).
Q9
True / FalseThe CREATE TABLE statement in SQL Server cannot define a primary key constraint if the key involves more than one column.
SQL Server supports composite primary keys involving multiple columns, which can be defined using the CREATE TABLE statement.
Q10
True / FalseIn SQL Server, the CREATE TABLE statement can include a CHECK constraint to enforce a condition on values in a column.
CHECK constraints can be defined in SQL Server using the CREATE TABLE statement to enforce conditions on column values.
Q11
True / FalseThe CREATE TABLE statement in SQL Server can be used to create a table with an identity column, which automatically generates unique values.
Identity columns in SQL Server automatically generate unique values and can be defined using the CREATE TABLE statement.
Q12
True / FalseIn SQL Server, the CREATE TABLE statement allows you to define the collation for character data, which controls the sorting and comparison rules.
Collation settings can be specified for character columns in SQL Server using the CREATE TABLE statement to control sorting and comparison.
Q13
True / FalseThe CREATE TABLE statement in SQL Server can be used to define a table with partitioning, which helps manage large tables by dividing them into smaller pieces.
Table partitioning can be defined in SQL Server using the CREATE TABLE statement to manage large tables by splitting them into smaller, manageable pieces.
Q14
True / FalseIn SQL Server, a table created with the CREATE TABLE statement cannot have columns with the same names as columns in a table from an ORACLE database linked via a linked server.
SQL Server allows creating tables with columns that have the same names as columns in tables from other databases, including ORACLE, when using linked servers.
Q15
True / FalseThe CREATE TABLE statement in SQL Server supports creating temporary tables that are automatically dropped when the session ends.
Temporary tables can be created in SQL Server using the CREATE TABLE statement, and they are automatically dropped when the session that created them ends.