[AccessD] Pushing A2K Data to SQL2K - S-L-O-W!:

Hi Gustav,	No, I haven't tried, and I'm still learning the new, mostly
undocumented, schema of the new app.  Do you think the indexes account for a
large chunk of the five hours?  Being new to SQL, would I have to manually
record and recreate the indexes, or can I store the index 'defs'
temporarily?

TIA,
Ron


-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of Gustav Brock
Sent: Tuesday, February 04, 2003 2:41 PM
To: Ron Moore
Subject: Re: [AccessD] Pushing A2K Data to SQL2K - S-L-O-W!:


Hi Ron

Have you tried dropping the indexes on the target table during the
appending?
Of course, recreate them afterwards.

/gustav


> *cross-posted to SQL & Access Forums*

> I'm migrating/converting data from an Informix DB to a SQLServer2K app
using
> A2K as the middleware.  The final append query selects records from a
buffer
> table and inserts them into a SQL table through an ODBC connection.  The
> push of the largest table takes almost 5 HOURS! :-((((   The Windows Task
> Manager shows A2K and the specific DB 'toggling' between 'Running' and
'Not
> Responding', but the process does finish.

> 107,850 Records in A2K table.  72 Fields.  DB size (compressed before
push)
> is 86Mb (was 346Mb).

> Do I have to live with this lack of speed?  This is for a pilot which will
> be built from 'scratch' MANY times before it goes to production.

> TIA,
> Ron Moore
> Sr. Database Administrator
> Comtech PST Corp.
> Melville,  NY
> www.comptechpst.com

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com