You have a Microsoft Office SharePoint Server 2007 Service Pack 2 (SP2) server farm.
You deploy SharePoint Server 2013 Service Pack 1 (SP1). You attach the content
databases from the SharePoint Server 2007 server farm to SharePoint Server 2013 Service
Pack 1 (SP1). You need to identify whether the content databases contain any
customizations that cannot be used by SharePoint Server 2013 Service Pack 1 (SP1).
What should you run?
A.
the test-spcontentdatabase cmdlet
B.
the psconfig.exe command
C.
the spmetal.exe command
D.
the mount-spcontentdatabase cmdlet
Explanation:
Detailed Description
This cmdlet contains more than one parameter set. You may only use parameters from one parameter set, and
you may not combine parameters from different parameter sets. For more information about how to use
parameter sets, see Cmdlet Parameter Sets.
Use the Test-SPContentDatabasecmdlet to test a content database against a Web application to verify all
customizations referenced within the content database are also installed in the web application. This cmdlet
can be issued against a content database currently attached to the farm, or a content database that isnot
connected to the farm. It can be used to test content databases from SharePoint 2013 Products and from
SharePoint Products and Technologies.
Note:
The Test-SPContentDatabasecmdlet does not change any of the data or structure of the content
database, but can cause load on the database while the checks are in progress, which could temporarily
block use of the content database. This cmdlet should only be used against a content database that is
currently under low or no usage.
Input Types
Return Types
Example
—————————-EXAMPLE 1———————–
Copy
Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename
This example tests the WSS_Content_DBcontent database against the sitenameWeb application, and
returns a list of issues.
—————————-EXAMPLE 2———————–Copy
$DB = Get-SPContentDatabase -site http://contoso.com
Copy
Test-SPContentDatabase $DB -showrowcounts
This example gets the content database that contains the site collection at http://contoso.com, and then
tests the database against the Web application thathosts it to determine issues. Together with displaying the
list of issues, by specifying the ShowRowCountsparameter, this also returns the table size metrics from the
content database.
http://technet.microsoft.com/en-us/library/ff607941.aspx