DPM 2012 RU3 - DPMDB database and log file could get very big when running SharePoint Catalog Task

Hi all,

DPM 2012 RU3 has introduced a spelling mistake in SQL Store Procedure leading to dysfonction of Sharepoint Catalog task: http://social.technet.microsoft.com/Forums/en-ZA/dataprotectionmanager/thread/e0e70be6-7249-438d-b43c-a0456f7c1338

The store procedure prc_PRM_SharePointRecoverableObject_Update should be modified. 

Open Microsoft SQL Manager Studio :

Go to DPMDB / Programmability / Stored Procedures

### before ###
USE [DPMDB]
GO
/****** Object: StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update] Script Date: 11/04/2012 09:53:37 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update]
(
@Caption nvarchar(40),
@ComponentType nvarchar(16),
@RecoverableObjectId BIGINT
)
AS
DECLARE @error INT,
@rowCount INT
SET @error = 0
SET NOCOUNT ON
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption,
ComponentType = @ComponentType
WHERE RecoverableObjectId = @RecoverableObjectId
SELECT @error = dbo.udf_DPS_CheckRowCount(1)
SET NOCOUNT OFF
RETURN @error

### After ###
USE [DPMDB]
GO
/****** Object: StoredProcedure [dbo].[prc_PRM_SharePointRecoverableObject_Update] Script Date: 11/04/2012 09:53:37 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[prc_PRM_SharePointRecoverableObject_Update]
(
@Caption nvarchar(40),
@ComponentType nvarchar(16),
@RecoverableObjectId BIGINT
)
AS
DECLARE @error INT,
@rowCount INT
SET @error = 0
SET NOCOUNT ON
-- UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption
UPDATE tbl_RM_SharePointRecoverableObject SET Caption = @Caption,
ComponentType = @ComponentType
WHERE RecoverableObjectId = @RecoverableObjectId
SELECT @error = dbo.udf_DPS_CheckRowCount(1)
SET NOCOUNT OFF
RETURN @error

This bug will most likely fixed in the SP1.

Available: Update Rollup 3 for System Center 2012

List of issues that are fixed in Update Rollup 3 for System Center 2012 - Mostly for SharePoint, feel free to apply or wait for SP1 - :

Update Rollup 3 for System Center Data Protection Manager 2012 (KB2751230)

UR3 have been released via Microsoft Update.
For more information and to download: http://support.microsoft.com/kb/2756127/en-us

Issue 1
After you upgrade System Center Data Protection Manager 2010 to System Center Data Protection Manager 2012, the tape management report does not display overdue tapes.

Issue 2
System Center Data Protection Manager 2012 Client Protection does not scale to the limits that are expected.

Issue 3
When you try to specify a client computer name in the DPMServerName attribute by using Windows PowerShell, Windows PowerShell crashes.

Issue 4
When the name of a Microsoft SharePoint site collection contains a space, and you perform a SharePoint item-level recovery operation in System Center Data Protection Manager 2012, the operation fails.

Issue 5
After you rename a SharePoint site in System Center Data Protection Manager 2012, you cannot restore the site.

Issue 6
The SharePoint Recovery Point Status Report displays incorrect data in System Center Data Protection Manager 2012.

Issue 7
A bare metal recovery fails in certain situations.