Which three actions should you perform in sequence?

You administer a Microsoft SQL Server 2012 environment that contains a production SQL Server 2005 instance
named SQL2005 and a development SQL Server 2012 instance named SQL2012.
The development team develops a new application that uses the SQL Server 2012 functionality.
You are planning to migrate a database from SQL2005to SQL2012 so that the development team can test
their new application.
You need to migrate the database without affecting the production environment.
Which three actions should you perform in sequence?(To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.)

Build List and Reorder:

You administer a Microsoft SQL Server 2012 environment that contains a production SQL Server 2005 instance
named SQL2005 and a development SQL Server 2012 instance named SQL2012.
The development team develops a new application that uses the SQL Server 2012 functionality.
You are planning to migrate a database from SQL2005to SQL2012 so that the development team can test
their new application.
You need to migrate the database without affecting the production environment.
Which three actions should you perform in sequence?(To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.)

Build List and Reorder:

Answer:

Explanation:

Reference: http://msdn.microsoft.com/en-us/library/ms177429.aspx



Leave a Reply 4

Your email address will not be published. Required fields are marked *


Yommy O.

Yommy O.

1. Perform FULL backup of DB in SQLServer2005
2. Restore the full DB backup to an SQLServer2012 instance
3. In SSMS 2012, right-click restored DB => Facet => CompatibilityLevel = Version110

sqljedi

sqljedi

You need to migrate the database without affecting the production environment in 3 actions.

1. Perform a VSS backup on the database on SQL2005.
2. Restore the VSS backup on SQL2012.
3. Change the compatibility level for the database to 110 on SQL2012.