Download Administering Microsoft SQL Server 2012-2014 Databases.70-462.TestKing.2019-02-10.184q.vcex

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

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

Requirements for Restoring Pages A page restore is subject to the following requirements:The databases must be using the full or bulk-logged recovery model. Some issues exist if you are using the bulk-logged model. For more information, see the following section. Pages in read-only filegroups cannot be restored. Trying to make a filegroup read-only will fail if there is a page restore going on at the same time in the filegroup. The restore sequence must start with a full, file, or filegroup backup. A page restore requires an unbroken chain of log backups up to the current log file, and they must all be applied so that the page is brought up to date with the current log file. As in a file-restore sequence, in each restore step, you can add more pages to the roll forward set. A database backup and page restore cannot be run at the same time. Bulk-logged Recovery Model and Page Restore For a database that uses the bulk-logged recovery model, page restore has the following additional conditions:Backing up while filegroup or page data is offline is problematic for bulk-logged data, because the offline data is not recorded in the log. Any offline page can prevent backing up the log. In this cases, consider using DBCC REPAIR, because this might cause less data loss than restoring to the most recent backup. If a log backup of a bulk-logged database encounters a bad page, it fails unless WITH CONTINUE_AFTER_ERROR is specified. Page restore generally does not work with bulk-logged recovery. A best practice for performing page restore is to set the database to the full recovery model, and try a log backup. If the log backup works, you can continue with the page restore. If the log backup fails, you either have to lose work since the previous log backup or you have to try running DBCC must be run with the REPAIR_ALLOW_DATA_LOSS option.

When replication is configured, a set of agent profiles is installed on the Distributor. An agent profile contains a set of parameters that are used each time an agent runs: each agent logs in to the Distributor during its startup process and queries for the parameters in its profile.For merge subscriptions that use Web synchronization, profiles are downloaded and stored at the Subscriber. If the profile is changed, the profile at the Subscriber is updated the next time the Merge Agent runs. For more information about Web synchronization, see Web Synchronization for Merge Replication. Replication provides a default profile for each agent and additional predefined profiles for the Log Reader Agent, Distribution Agent, and Merge Agent. In addition to the profiles provided, you can create profiles suited to your application requirements. An agent profile allows you to change key parameters easily for all agents associated with that profile. For example, if you have 20 Snapshot Agents and need to change the query timeout value (the - QueryTimeout parameter), you can update the profile used by the Snapshot Agents and all agents of that type will begin using the new value automatically the next time they run. You might also have different profiles for different instances of an agent. For example, a Merge Agent that connects to the Publisher and Distributor over a dialup connection could use a set of parameters that are better suited to the slower communications link by using the slow link profile.

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