Hi,
I have seen several questions about migrating from SQL Server to SAPDB
using DTS ( Data Transformation Service), but no answer yet...
Using the Import/Export-Wizard didn't work for me either (Sometimes
some tables where created, sometimes not; most of the time DTS simply hang up) ->> Threading/Timing-Problem ?
Here is what helped me:
Using DTS,in step "Save,schedule and replicate package"
uncheck "Run immediately"
check "Save DTS Package" , choose "Visual Basic File" and proceed
Open the File with Visual Basic.
Add the reference ( Project -> References ) to "Microsoft DTSPackage Object Library"
Search the File for "oConnection.Password" , uncomment the lines and set the
adequate passwords (if needed)
Search for "oStep.ExecuteInMainThread = False" and change all to "true"
Changing "goPackage.FailOnError = False " to "true" enables the script to 'talk' to you...
Save the Project and try...
If it's still not working, there might be a problem with Table/ColumnNames or typeConversion:
In the Script, all TableNames are enclosed in doubleQuotes ( " ); in SAPDB then the name is
casesensitive (right?). If you get a message like "Base table not found; ..." change
all the TableNames to capitals ( especially in the Create Table - Task )
Another interesting feature (?) was the conversion of FLOAT:
If you get an error like " General Error;... Missing delimiter: )." take a look at the FLOATs.
I had one FLOAT-column and in the script I found " Create Table... <columnname> FLOAT (15NULL ".
Changing "(15NULL" to "(15) NULL" helped a lot...
Further Debugging:
Importing data consists of 2 steps for each table:
1. Create table
2. Copy data
All those steps are added as tasks to a package and then the whole package is executed ("goPackage.Execute"),
so if somewhere a problem occurs it is hard to tell where (you might get a hint by looking in SQL-Studio which tables were created...)
To narrow down the problem, for each step you can set "oStep.DisableStep = true" and the step is skipped.
Hope this helps,
good luck,
Chris
BTW: any comments or better solutions are appreciated...
> -----Original Message-----
> From: Steve Brett [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 16, 2002 12:23 PM
> To: Sapdb. General@Listserv. Sap. Com (E-mail)
> Subject: SQL Server 2k > SAP
>
>
> Hi,
>
> Does annyone have any experience of using OBDC and DTS in SQL
> Server 2000 to
> populate SAP dbs ?
>
> I seem to be having loads of problems including no data
> transfer unless the
> table exists already in SAP ....
>
> Steve Brett
> SID
> EMIS Ltd.
>
>
