Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 SQLBase import error into MS SQL Server using DTS & ODBC

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2003-02-24 : 19:34:51
Groveraus writes "I am trying to create a DTS package that will run every night to copy data out of a Centura/Gupta SQLBase database into a MS SQL Server database.

I have downloaded and installed all the latest ODBC drivers for SQLBase and MDAC.

I use the MS SQL Server DTS Wizzard to make the ODBC connections, create and copy the data. Checking the Preview shows that there is data in the table that I am copying (only testing on one table at a time). The SQL Server creates the table with the correct table names and then tries to copy data. This is were it all falls over in a heap.

The pop-up title bar says "Copy Data from 'abc' to 'def' Step". I get an error that says "Column name 'xxx' was not found.".

I have a long winded workaround of unloading the data into an ascii file from the SQLBase database and then using DTS to load the data into SQL Server. This works but is not the prefered method.

Any help would be greatly appreciated.
Thanks "

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-02-24 : 20:04:41
I don't like to admit this, but at my previous job, I was also a SQLBase DBA. I was able to import/export data from/to SQLBase 7.5 into SQL Server 7.0 using DTS. I would bet that your problem is either with the ODBC driver for SQLBase (make sure that you are using the correct version which is not necessarily the latest version), the column name of the table (maybe it's using a reserved word or something), or that the table isn't being created correctly on the SQL Server side. Try creating the table using your DDL script in SQL Server and then importing the data.

That ascii file thing that you are talking about is definitely not what you want to do since I know how long SQLBase takes to output the data into that file.

Go to Top of Page
   

- Advertisement -