Hi all, We have a 2-tier SCCM infrastructure with 1 central site and 4 child (primary) sites. All sites are ConfigMgr 2007 R2 SP2 and are hosted on Windows 2008 servers with SQL 2005 SP3. However, for some reason one of the child sites is running on SQL 2005 SP2. I know this poses compatibility issues with Windows 2008 servers and is reason enough to upgrade the SQL to SP3. However, Im a bit wary of doing so because the child site is currently replicating from the central site (which is big) and this takes a while. What is the best approach into upgrade the DB to SP3? I could stop the SMS executive service on the child site, perform the upgrade and restart the services, but I have no idea how this will affect the replication process? (If at all) Any insights into this are highly appreciated! RegardsCheck out my blog "System Management Compendium" at www.sylvari.org

Hi, Your approach sounds like a good solution. Replication from the central site will "wait" while upgrading the site database and automatically start again when a connection can be made.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Kent, Thanks for your fast reply. I just hope the replication isn't bothered by the changes made through the SP3 installation. I'll make some preparations and will post the outcome here. RegardsCheck out my blog "System Management Compendium" at www.sylvari.org

Im a bit wary of doing so because the child site is currently replicating from the central site (which is big) and this takes a while. So it's a brand new site and the initial replication is still going on?

Torsten, Well the child site is new, but we have serious replications issues with it. I have checked everything in the site and replication IS working, but there are 22k files in \objmgr.box\INCOMING\Retry. Rest of the statistics (file counts) are perfectly decent. I cannot find what's taking so long, processes don't seem to peek at all, memory doesn't peak, DB isn't malfunctioning. Objreplmgr.log shows a repeating (but with diff. values ofc): File notification triggered. Successfully replicated SMS Object CF0B3961-9503-4B18-B1BC-5E09B839A527, ReplVarFileName:D:\Microsoft Configuration Manager\inboxes\objmgr.box\t21wdgqw.TMP Successfully replicated to all sites. Object - ID= CF0B3961-9503-4B18-B1BC-5E09B839A527 - Name= CF0B3961-9503-4B18-B1BC-5E09B839A527 Successfully processed Object CF0B3961-9503-4B18-B1BC-5E09B839A527 Set last row version to 0x0000000003CEFB56 Successfully deleted notification file D:\Microsoft Configuration Manager\inboxes\objmgr.box\1030.MEN(0) replmgr.log shows: Waiting for incoming replication files... Moved incoming replication file to D:\Microsoft Configuration Manager\inboxes\auth\dataldr.box\a1k9x2x6.MIF Moved incoming replication file to D:\Microsoft Configuration Manager\inboxes\auth\dataldr.box\e1soo835.MIF {this goes on in batches of ~15-20} Waiting for incoming replication files... Monitoring inbox file count shows a fluctuating amount of files in the related inboxes folders. Like I said, replication IS occuring since all (or at least most of them for as far as I can see) elements are replicated from central to the primary site. Honestly, I have no idea what to do next!Check out my blog "System Management Compendium" at www.sylvari.org