- A.Apply a bulk update lock to the table.
- B.Use separate client connections to load the files into the table simultaneously.
- C.Create a clustered index on the table.
- D.Specify the Full Recovery model for the database.
- E.Specify the Bulk-Logged Recovery model for the database.
- A.Perform. a combination of full database and filegroup backups.
- B.Perform. a combination of full database and file backups.
- C.Perform. a combination of full database, differential, and transaction log backups.
- D.Back up the data to a local tape drive.
- E.Back up the data to a network share, and then use enterprise backup software to write the disk backups to tape.
- A.Implement merge replication.
- B.Implement snapshot replication.
- C.Implement transactional replication.
- D.Schedule replication to run continuously.
- E.Schedule replication to run during off-peak hours.
- A.Shrink the empty data file on drive E. Place the new data file and the new log file on drive E.
- B.Shrink the empty data file on drive E. Backup and shrink the log file on drive C to 2 GB. Place the new data file on drive E and the new log file on drive C.
- C.Shrink the data file on drive D to 1 GB, and then shrink the data file on drive E to 2 GB. Place the new data file on drive D and the new log file on drive E.
- D.Shrink and delete the data file on drive C, and then shrink the database files on drives D and E so that they are both 2 GB. Place the new data file and the new log file on drive C.
- A.Add a 2-GB transaction log to drive D, a 3-GB data file to drive E, and a 3-GB data file to drive F
- B.Add a 1-GB transaction log to drive C, a 1-GB transaction log to drive D, a 3-GB data file to drive E, and a 3-GB data file to drive F
- C.Add a 1-GB transaction log to drive E, a 1-GB transaction log to drive F, a 3-GB data file to drive E, and a 3-GB data file to drive F
- D.Add a 2-GB transaction log to drive F, a 3-GB data file to drive D, and a 3-GB data file to drive E
- A.Use the ALTER COLUMN clause of the ALTER TABLE statement to change data types in the source tables. Change the data types so that they will use the lowest precision and scale values of the data that will be transferred.
- B.Use the ALTER COLUMN clause of the ALTER TABLE statement to change data types in the destination tables. Change the data types to reflect the highest precision and scale values involved in data transfer.
- C.Set a flag on each DTS transformation to require an exact match between source and destination columns.
- D.Set the maximum error count for each DTS transformation task equal to the number of rows of data you are importing. Use an exception file to store any rows of data that generate errors.
- E.Write Microsoft ActiveX script. for each DTS transformation. Use the script. to recast data types to the destinations precision and scale values.
- A.Use the spid 52 icon in the Current Activity window to discover which SQL statement is being executed
- B.Use the sp_who stored procedure to discover who is logged in as spid 52
- C.Use SQL Profiler to capture the activity of the user who is logged in as spid 52
- D.Use System Monitor to log the locks that are granted in the database
- A.Increase the maximum file size of Sales_Data to 1,500MB.
- B.Use the DBCC SHRINKDATABASE statement.
- C.Set automatic file growth to 10 percent.
- D.Create another data file named Sales_Data2 in a new SECONDARY filegroup.