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.
| Author |
Topic |
|
cbuschel
Starting Member
3 Posts |
 Posted - 2002-08-15 : 13:39:39
|
| I'm trying to import a number of tables from a Pervasive Btrieve DB into an SQL Server 7 DB using DTS. I seem to be able to make and ODBC connection to the Btrieve DB but the import fails immediately after it starts copying data to the newly created table in SQL Server. The error I receive reads:"Error at Source for Row number 2870. Errors encountered so far in this task: 1. Unspecified error[Maximizer][ODBC Driver][Btrieve Database]Buffer is too small."Now the the Pervasive Server's Communication and MKDE buffer sizes are set to about 64500 B of a maximum 65000 B. The Read buffer size is set to about 64000 B out of a maximum of 65500 B. The table I'm trying to import is only about 29000 rows and I have no problem importing it into MS Access 2000 and then importing it into SQL Server from there. The ODBC driver I'm using is a Maximizer ODBC Driver from Multiactive Software. I don't think it is a buffer issue on the SQL Sever end because I have been successful when importing tables up to 300,000 rows from a different database.Is this truly a buffer error? Could it be an ODBC error? Any suggestions?Thanks in advance!Cam |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-15 : 13:50:26
|
| If I had to guess, I'd say that DTS is trying to import the whole table as one batch (this is the default), and that the amount of data from row 1 to row 2870 exceeds the buffer size for the Maximizer ODBC driver.See if setting the "Use fast load" and "batch size" settings affect the import. Try a batch size of 100 as a start. That will commit every 100 rows imported and should flush the buffer for each batch.Also try reducing the buffer size, say to 32,000 bytes, and see if it effects the number of rows imported. Do this both with and without the batch size settings.Failing that, you should contact the people who make the ODBC driver and see if they have another workaround. Also, see if any of the vendors here:http://ourworld.compuserve.com/homepages/Ken_North/oledbVen.htmMake an OLE DB provider that works with your Btrieve data. ODBC is really starting to get creaky, and OLE DB usually doesn't have the kind of buffer quirks and other stuff that ODBC does. |
 |
|
|
cbuschel
Starting Member
3 Posts |
Posted - 2002-08-15 : 15:34:51
|
| I'm having a little trouble finding the "fast load" and "batch size" options. I opened the properties for my DTS package but I can't see a way to set these options. Can you tell me where to find these settings? Are they only available in SLQ Server 2000 because I'm currently using 7.0?Thx againCam |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-15 : 15:42:21
|
| Right-click on the data transform task (the gray/black arrow) and choose Properties. The settings should be on the Advanced tab. |
|
|
|
jsiedliski
Yak Posting Veteran
61 Posts |
Posted - 2004-02-12 : 15:13:13
|
| I am having issues finding the right driver for Pervasive Btrieve DB. I want to import data from Pervasive Btrieve DB to SQL Server 2000.What data source did you specify?What driver are you using?Did this driver / data source option come with the SQL Install or did you have to obtain it and istall yourself?Any help is appreciated.Thanks,JackRome was not built overnight. |
|
|
|
|
|
|
Error importing from Pervasive Btrieve DB