Inventory Transfer During the Attach Process is Slow

Article ID: Q153250

----------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Systems Management Server, versions 1.0 and 1.1
----------------------------------------------------------------------

SYMPTOMS
========

When a child site attaches to a parent site, it transfers the existing
inventory in its database to its parent. It does so by dumping all the
inventory from the database into four binary files. It then sends the
binary files to its parent site, where the parent's despooler reconstructs
them into individual MIFs and sends them to the dataloader to be loaded
into the parent site's database. For Systems Management Server 1.0 and 1.1
this inventory transfer of a large database can take many hours to
complete.


RESOLUTION
==========

The inventory update process has been greatly enhanced in SMS 1.2.  The
child site now dumps the inventory information into multiple files using
bulk operations.  On the receiving end the data is put directly into the
database again using bulk operations.

STATUS
======

Microsoft has confirmed this to be a problem in Systems Management Server
version 1.1. This problem has been corrected in Systems Management Server
version 1.2.

KBCategory: kbnetwork kbbug1.10 kbfix1.20
KBSubcategory: smsinv
Additional reference words: prodsms 1.00 1.10 invupd.dll invupd

===========================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" 
WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER 
EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS 
FOR A PARTICULAR PURPOSE.  IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS 
SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, 
INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, 
EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE 
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION OR 
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE 
FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1996.
