Practice Questions: Building Tables

SQL Server will not create a table of more than 8060 bytes, so the table creation fails.

SQL Server creates the table as input and warns you not to insert more than 8060 bytes.

SQL Server creates the table but adjusts the length of the last column(s) to fit the 8060 bytes.

SQL Server creates the table and moves the columns that would cause the row to exceed 8060 bytes to the next page.

SELECT MAX (orderid) from ORDERS

You have to insert the order, then find the orderid value within one transaction so that nobody else adds an order and changes the orderid number before you are finished using it:

BEGIN TRANINSERT Orders...... SELECT MAX (orderid) from OrdersINSERT [Order Details]...COMMIT TRAN

SELECT @@identity

Use an Identity column in the Order Details table. Use an explicit transaction to make sure that the two Identity columns stay synchronized:

BEGIN TRANINSERT Orders...... INSERT [Order Details]COMMIT TRAN

always add a column to provide a unique identifier to be used in the merge.

add a column with the Identity property if it doesn't find one.

add a column with the RowGUID property if it doesn't find one.

do nothing—you have to make sure all the identifier columns are in place before setting up merge replication.