I'm using DTS to import data into SQL. Client Access ODBC is the driver I'm using. Any reason why DTS would move so slow pulling data down.
I can run that same import from a local access database and it will
run three times faster.
thx
jmWhat's the data in on the AS/400?|||JDE.. But the file isn't vanilla JDE.. Actually, I just create a File using query first, then I use DTS to import/translate..|||Can't you dump the data on the 400 then just copy and load it?|||Originally posted by jmayo
I'm using DTS to import data into SQL. Client Access ODBC is the driver I'm using. Any reason why DTS would move so slow pulling data down.
I can run that same import from a local access database and it will
run three times faster.
thx
jm
COULD BE YOUR NETWORK SERVICES, CHECK OUT HOW FAST IS WORKING YOUR NETWORK, IF YOU ARE WORKING ON WINDOWS, CHECK OUT TERMINAL SERVICES|||are there any tranformations?
how is your package transforming the data?
are you using activex operations to perform the x-foms?
activex is single threaded in dts that could slow down operations
what is happpening on the SQL Side once you import the data
are those tables indexed and do they have enabled constraints on them?
constraint checking can slow down an import
so can an index load.
Disable your constraints and indexes before you perfom a bulk load|||Thanks for all the suggestions..
I will look into each of them..
To answer one of the questions, yes I'm using terminal services..
thx
jm|||Originally posted by jmayo
I'm using DTS to import data into SQL. Client Access ODBC is the driver I'm using. Any reason why DTS would move so slow pulling data down.
I can run that same import from a local access database and it will
run three times faster.
thx
jm
We pull data out of the AS/400 here and there are two areas which will be the cause of performance problems.
1)The speed of the network connection.
2)the size of the tables you are transforming.
Not much you can do apart from increase your network bandwith and the cards on the SQL Server and the AS/400 (I think we have Gigabit Ethernet cards on each end)
For every thousand rows is takes approx three seconds - so if you are around this then you're doing OK.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment