you should be able to start the correct sqlagent job to invoke the replication cycle to get them back in sync.

This should work automaticaly if you have setup logshipping.

Check BOl for "log shipping, overview"

Check your server's sqlagent if the jobs have been or are running ...

As always, there is no straight forward in  a relational environment

If you use it in a well-considered way you'll gain from it, else...

just to add to peterhe's reply :

1) connection pooling works for the full connection string. and must match each and every bit...

If you have it captured to file , save the file to a sqlserver and launch queries against that table.

This way you have a quick overview of your large consumers...

did you use sql-profiler to look what's going on ?

offcourse .... your previous reply got me back to hinking ....

use yourdb

go

DECLARE @TableName nvarchar(261)

DECLARE @SQLStatement nvarchar(4000)

DECLARE TableList CURSOR LOCAL FAST_FORWARD READ_ONLY  FOR

SELECT

    QUOTENAME(TABLE_SCHEMA) +

    N'.' +

    QUOTENAME(TABLE_NAME)

FROM

    INFORMATION_SCHEMA.TABLES

WHERE EXISTS

    (

   ...

count_rows : my mistake. I mixed up DBCC UPDATEUSAGE  ('yourdb') with count_rows. which should be done after the reindex as well !