We recently upgraded our version of Replicate to and have noticed an issue for a full-load task. The source table is partitioned and the task hangs on the query listed below; eventually the task suspends the table. If I run the query in SSMS, it takes over 11 minutes to return a response. So, not sure what to do. We have no control over how the table is partitioned, since it comes from a 3rd party. Is there a way to increase the timeout so that it will wait longer? This seems to be a change in this release since we can run the same task on an older version of Replicate and it runs just fine and doesn't appear to use the query.

pf.name AS PartitionFunctionName, c.name AS PartitionKey
FROM sys.dm_db_partition_stats AS pstats
INNER JOIN sys.partitions AS p
ON pstats.partition_id = p.partition_id
INNER JOIN sys.destination_data_spaces AS dds WITH (NOLOCK)
ON pstats.partition_number = dds.destination_id
INNER JOIN sys.data_spaces AS ds
ON dds.data_space_id = ds.data_space_id
INNER JOIN sys.partition_schemes AS ps
ON dds.partition_scheme_id = ps.data_space_id
INNER JOIN sys.partition_functions AS pf
ON ps.function_id = pf.function_id
INNER JOIN sys.indexes AS i
ON pstats.object_id = i.object_id AND pstats.index_id = i.index_id AND dds.partition_scheme_id = i.data_space_id AND i.type <= 1
INNER JOIN sys.index_columns AS ic
ON i.index_id = ic.index_id AND i.object_id = ic.object_id AND ic.partition_ordinal > 0
INNER JOIN sys.columns AS c
ON pstats.object_id = c.object_id AND ic.column_id = c.column_id
WHERE pstats.object_id = OBJECT_ID(N'[schema].[tablename]', N'table')
GROUP by pf.name, c.name