By using an odbc connection you will suffer greatly in performance. If you want to get the data over in your life time I would suggest d/l the sql server native drivers at
http://www.microsoft.com/downloads/d...displaylang=en
and then by playing with the batch files that the MTK creates enabling the use of the drivers. to quote the MTK Support team:
Quote:
Take a look inside
DataMove_conversion_data.bat
You will see some lines that look like:
REM What is the label for the source database?
set SRC_DATABASE=SQL2000
REM Are you using a native driver to access the source database?
set SRC_NATIVE=FALSE
Change them, substituting the ip address of the host for hostname and the port number for port
REM What is the label for the source database?
set SRC_DATABASE=hostname ort
REM Are you using a native driver to access the source database?
set SRC_NATIVE=TRUE
If the system classpath does not already include msbase.jar, mssqlserver.jar, and msutil.jar, add those to the line:
set classpath=%USERDIR%mtk.jar;%USERDIR%xmistore.jar;% USERDIR%cwm.jar;%CLASSPATH%
If you are running the scripts on UNIX or LINUX, then you will make comparable changes to DataMove_conversion_data.sh
|
This will activate the drivers and you will pump data much faster.
The tool isnt streight forward, so if you have any questions you can ask here or you can e mail there support team. I will try to help as much as I can