While the "Export -> Cleanup process -> Import" can be easily done (as the
others have answered) - I have always pushed users AWAY from this "process"

What I offer to do is this:
1). Create a report that contains *metrics of % Cleanup / number of records,
etc* and the Data associated...
2). Schedule / Trend the report daily / weekly / monthly based upon their
estimated cleanup schedule
3). Have then edit the data *in the CMDB*

The reasons are many but here are the key thoughts behind my madness...

a). This gets the remedy administrators "out of the export / import
business" - we got better things to burn our time and efforts on (want that
bug looked at or for me to import a data-sheet!)
b). Mass data load - should be done off hours - who is paying for the
overtime
c). If 'other data' is messed with (say the request_ID) merge of records can
be in error
d). if a CI is deleted then merge will fail / create a new record (depends
on your import settings)
e). if a user updates the CI and you overwrite it - possibly other "old
data" is now back in the system. - definately resulting in an angry user!!
F). *managers like reports that show progress* - say you have 5000 records
to clean up - isn't it better to see a weekly progress of say 500 records a
week being cleaned? This sets 'resolution expectation commitment' / etc!

HTH
Robert

On Thu, Sep 25, 2008 at 8:40 AM, Jase Brandon <[EMAIL PROTECTED]> wrote:

> ** Hello All,
> I know this is probably an easy question, but I can't remember the answer,
> it's been awhile since someone asked me this question and never regarding
> CMDB data with 7.1.
>
> We have a ton of Network Port CI Data that needs to be "Cleaned Up".
> User is asking if I can send him an .csv dump of all Network Port CMDB CI
> Data, let him modify it, then we reimport it into the Network Port CI Form.
> I am leary, #1 - because of the CMDB architecture and the danger of
> importing data with the inner joins, etc.
> #2, Remedy Import only uses .arx files, and I can't remember if there is a
> way to convert an .arx to a .csv, etc.
>
> I am leaning toward suggesting a manual update of the CI records to ensure
> data integrity. Agree?
>
> Can anyone enlighten me, please?
>
> Thanks in Advance,
>
> Jase
>
> ARS 7.1 Patch 002
> Windows Server 2003
> SQL Server 2005
> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___




-- 
If it were not for the gutter, my mind would be homeless!

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to