Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Reading DBISM table from SQL Server 2005/2008
Wed, Sep 30 2009 3:58 AMPermanent Link

Hans Peer
How can I read data from a DBISAM table using the DBISAM 4 drivers on a SQL Server 2005 or 2008. I created a DBISM DSN but I can not read data using:

SELECT * FROM OPENROWSET('MSDASQL','TEST',adres)
OR
SELECT * FROM OPENDATASOURCE('MSDASQL','DSN=TEST')...Adres

Also a linked server gives problems:
EXEC sp_dropserver 'TEST'
GO

EXEC sp_addlinkedserver
@server='TEST',
@srvproduct='DBISAM 4 ODBC Driver',
@provider='MSDASQL',
@provstr='DSN=TEST'
GO

SELECT * FROM OPENQUERY(TEST, 'select * from adres')
go

If you have a solution please let me know!

--
Hans
Wed, Sep 30 2009 8:12 AMPermanent Link

Hans Peer
I need 64 bits drivers for MY SQL Server 64 bits. This works on my SQLSERVER Express on the same machine:

SELECT * FROM OPENROWSET('MSDASQL','DRIVER={DBISAM 4 ODBC
Driver};ConnectionType=Local;FILEDSN=C:\Users\hans\Documents\test.dsn;CatalogName=Y:\TEST\DATA','SELECT * FROM table')

A 64 bits driver would help Smileor it must be possible to access the 32 bits drivers on a SQL Server 64 bits, but I think this is not possible.
Wed, Sep 30 2009 12:06 PMPermanent Link

"Raul"
Hopefully somebody will know an easier answer.

I had a somewhat similar problem with integration services - default job
uses 64 bit executables which could not access to 32bit data sources.. As i
recall we were able to add a custom job command step that runs 32bit version
of dtexec (MS KB had some articles on it).
As a workaround you could try to use integration services to import the
DBISAM into intermediate sql table and then access it from there (this
assumes you don't need real-time data access and are ok (re)importing it
every X minutes/hours)

Raul


"Hans Peer" <hanspeer@gmail.com> wrote in message
news:2C9880FC-C5FD-427A-B631-989563816DAD@news.elevatesoft.com...
>I need 64 bits drivers for MY SQL Server 64 bits. This works on my
>SQLSERVER Express on the same machine:
>
> SELECT * FROM OPENROWSET('MSDASQL','DRIVER={DBISAM 4 ODBC
> Driver};ConnectionType=Local;FILEDSN=C:\Users\hans\Documents\test.dsn;CatalogName=Y:\TEST\DATA','SELECT
> * FROM table')
>
> A 64 bits driver would help Smileor it must be possible to access the 32
> bits drivers on a SQL Server 64 bits, but I think this is not possible.
>

Wed, Sep 30 2009 12:55 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Hans,

<< I need 64 bits drivers for MY SQL Server 64 bits. >>

Unfortunately we don't have a 64-bit ODBC Driver yet.  We're waiting on a
64-bit compiler.

<< A 64 bits driver would help Smileor it must be possible to access the 32
bits drivers on a SQL Server 64 bits, but I think this is not possible. >>

You are correct.  64-bit applications cannot access 32-bit DLLs, and
vice-versa.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Nov 2 2010 5:23 PMPermanent Link

Vitalinka

Hi there

I have a DBISAM database. I want to transfer data from there to SQL Server 2005 (64 bit) using Integration Services. I installed the 32 bit DBISAM driver on SQL Server 2005 (64 bit) system and I was able to add it to ODBC data sources using odbcad32.exe. I created a new package for data transfer in Integration Services (so later I can schedule a  job to run my Integration Services package ). However, when I try to create a new ADO.NET connection and choose DBISAM ODBC data source I receive an error message.
My understanding is that I can not use a 32 bit driver on a 64 bit SQL Server.
Is there a way around this issue I run into?

Any prompt replies will be very much appreciated!

Vitalinka.



"Raul" wrote:

Hopefully somebody will know an easier answer.

I had a somewhat similar problem with integration services - default job
uses 64 bit executables which could not access to 32bit data sources.. As i
recall we were able to add a custom job command step that runs 32bit version
of dtexec (MS KB had some articles on it).
As a workaround you could try to use integration services to import the
DBISAM into intermediate sql table and then access it from there (this
assumes you don't need real-time data access and are ok (re)importing it
every X minutes/hours)

Raul


"Hans Peer" <hanspeer@gmail.com> wrote in message
news:2C9880FC-C5FD-427A-B631-989563816DAD@news.elevatesoft.com...
>I need 64 bits drivers for MY SQL Server 64 bits. This works on my
>SQLSERVER Express on the same machine:
>
> SELECT * FROM OPENROWSET('MSDASQL','DRIVER={DBISAM 4 ODBC
> Driver};ConnectionType=Local;FILEDSN=C:\Users\hans\Documents\test.dsn;CatalogName=Y:\TEST\DATA','SELECT
> * FROM table')
>
> A 64 bits driver would help Smileor it must be possible to access the 32
> bits drivers on a SQL Server 64 bits, but I think this is not possible.
>
Thu, Nov 4 2010 3:54 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Vitalinka,

<< I have a DBISAM database. I want to transfer data from there to SQL
Server 2005 (64 bit) using Integration Services. I installed the 32 bit
DBISAM driver on SQL Server 2005 (64 bit) system and I was able to add it to
ODBC data sources using odbcad32.exe. I created a new package for data
transfer in Integration Services (so later I can schedule a  job to run my
Integration Services package ). However, when I try to create a new ADO.NET
connection and choose DBISAM ODBC data source I receive an error message.
My understanding is that I can not use a 32 bit driver on a 64 bit SQL
Server. Is there a way around this issue I run into?  >>

Answered via email - you cannot mix 32-bit DLLs (DBISAM ODBC Driver) with a
64-bit application, so the only solution is to use the 32-bit version of SQL
Server 2005 for the transfer.

--
Tim Young
Elevate Software
www.elevatesoft.com
Image