Splitting the data into multiple imports will increase the rate at which they are imported, regardless of the target, as long as you have multiple threads available (one queue with multiple threads or separate queues with one thread).
You can disable archive/redo logging on the db, this will speed up the import. You can disable all unneeded remedy services as well (email, fb, escalations, etc), which will otherwise interrupt the throughput of the import. These come to mind at the moment. Axton Grams On 2/27/07, Cindy Sapochetti <[EMAIL PROTECTED]> wrote:
Hi All - Importing slightly less then 200,000 records from our current system into Remedy (ARS 7.0.01 patch 001, CMDB 2.0.1 patch 002, BMC Asset 7.0.02 patch 003, SQL Server 2003, Windows 2000 Server) from the command line (arimportcmd) using a private queue. Due to the way the CMDB is structured, I'm importing to a form that has a number of display only fields, where I have workflow looking up the name of the form to import to (i.e. AST:ComputerSystem, AST:NetworkPort, etc.), then it pushes about 10 fields to the appropriate form. ARS Server and DB server are on separate boxes, so there is network to contend with as well. Within the limitations of what I've mentioned, does anyone have any thoughts on how to speed up the import? I thought about splitting the source file up, running it on several different private queues, but most of this particular import is going into one of two forms, so I'm not sure if that would help. Any advice from this experienced crowd? Thanks, Cindy _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
