Database synchronization in Project Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
Microsoft SQL Server backup functionality backs up individual databases independently of each other. Because of this, if you have multiple databases that interact with each other, using standard SQL Server full or differential backups, related databases can be left in an inconsistent state when restoring.
The backup features in both the SharePoint Central Administration Web site and Stsadm command-line tool start standard SQL Server full or differential backups, so these tools also can leave related databases in an inconsistent state when restoring.
Microsoft Office Project Server 2007 has four dedicated databases for each instance of Microsoft Office Project Web Access, and also interacts with multiple SharePoint Products and Technologies databases. To avoid data inconsistencies and minimize the possibility of orphaned records, these databases should be synchronized during recovery operations. There are two primary methods of accomplishing this:
Use the full recovery model for each database and restore each database to the point of failure
Use the full recovery model for each database and restore each database to a marked transaction
If the active transaction log is still available after a hardware failure, then recovery to the point of failure is the preferred method. This assures minimal or no data loss and is the best option for recovering the databases to a consistent state.
If the active transaction log is damaged or unavailable for one or more related databases, we recommend that you recover to a named mark in the transaction log. This will synchronize the databases from a SQL transaction perspective and will minimize the risk of related databases being recovered to an inconsistent state.
Logical transactions
Both Office Project Server 2007 and SharePoint Products and Technologies employ logical transactions that take multiple SQL transactions to complete. Creating a site in SharePoint Products and Technologies, for example, initiates several SQL Server stored procedures and requires multiple transactions in SQL Server to accomplish. Such logical transactions include but are not limited to:
Creating a Web application or site collection
Provisioning a PWA site
Creating a Shared Services Provider
Logical transactions are usually the result of manually initiated administrative functions as opposed to regular functions done by users such as working with documents or lists, or entering time on a project.
If a database is restored to a point in time in the middle of a logical transaction, the Office Project Server 2007 or SharePoint Products and Technologies databases may have orphaned records and the application may not function correctly.
When restoring one or more databases, we recommend not restoring to a point in time where a logical transaction was taking place.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Project Server 2007.