ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on Windows XP it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
VadimIt should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on Windows XP it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on windows xp it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
Vadim
It should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on windows xp it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>
|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on windows xp it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
VadimIt should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on windows xp it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> I have a client server app that connects to sql server through ODBC, it
>> works fine when connecting to sql server 2005 32 bit, but when connecting
>> to sql server 64 bit from the client on windows xp it behaves strangely,
>> are there separate set of odbc drivers that one has to use to connect to
>> sql server 2005 64 bit, even from 32 bit machine.
>> Thank you
>> Vadim
>sql

ODBC Connects

Hi there!

Apologies to you Whiz kids for my ignorance herewith but I am trying to link an SQL database table to another database table from which I want to import data.

I'm an "Access" database girl who has had to face the fact that my database must now become an adult and join the 'big league' and so I am currently "playing" in SQL as I try to come to grips with this new programme. In Access, ODBC links were so easy! I used to go to TABLES, select LINK TABLES, select my ODBC link, log into the other database and, viola!, the tables would be there. I'd select the one/s I wanted and could even limit the fields that came though.

How does one do this in SQL? I do have an SQL manual here but have no idea where to even start reading in that (and it's a BIG MANUAL!)

If anyone can give me some direction on how to do this, I would be most appreciative. Remember, I'm a baby in SQL so please keep it simple!

Thanks everyone!!

MariaI'm not much ahead of you and perhaps there's a better way but...

SELECT * FROM OPENROWSET( parameters )

-- OR --

SELECT * FROM table_name1 JOIN OPENROWSET( parameters)

would appear to fit the bill.

Trouble is I can't get the 'parameters' bits figured out! (see my earlier post 'openrowset parameters").

Also DTS (Data Transformatin Services) makes it a snap to import via ODBC etc but is tedious to maintain for anything more than quick fixes.|||Do you want to use SQL Server databsese tables in Access? If you do than you have two choices:

1) Use the "old fashion" ODBC Databases tehnique: first create an ODBC chanel to your SQLServer database (From ODBC Manager in Control panel, or in Administrative Tools if you are using Windows 2000. You can create either a file datasource or a machine datasource). Then you can use this chanel in you link table wizard.

2) Starting with Access 2000, you can have a different type of database: .adp - Microsoft Access Project. This type of "database" allows you to use Access as a front-end to your SQLServer database. This means that you have tables, queries, storeproc in SQL Server and Forms and Reports in Access (all in one single project - .adp) For these kind of project native driversfor SQLServer are used. With Access 2000 you can use SQLServer 7 database, and with Access 2002 (XP) you can use SQLServer 2000 databases.

.Adp are version dependent as you can see from above paragraph. With "link method" you can use any type of SQLServer database you want. The only thing you have to have is the correct version of ODBC drivers for SQLServer. You can download ODBC drivers from microsoft. They are found in a package called "mdac" (Microsoft data access components)

IONUT

PS
As an own opinion it's a very good ideea to migrate your databases to SqlServer, but you should also stop using Access even for a front end. It's very slow with large amounts of data, it has runtime libraries anly from XP version (as much as I know) and therefore is very expensive (you have to have a MS Office licence for each seat). It's true that it is easy to code and it has one of the best report designer Microsoft has ever build, but... that's all

Good luck!|||How would one link the tables of one (production DB) to another SQL DB?

Thanks!!|||Hi there!

Thanks for that. I am actually, trying to leave out Access altogether and link the SQL database (which will be my data warehouse) to the source database where staff completed their service statistics. To date, I am using Access to link to the souce database but this is becoming too large and, as you will appreciate, is slow.

The ODBC connnection, that I am already using for the Access link/import is the same for SQL (according to the software house who produce the source database) so I just need now to tell SQL to go and get the specified fields/tables from the source database and dump them into new tables in this new SQL database. That's the bit I'm having the problems with.

Cheers!

Maria

Originally posted by ionut calin
Do you want to use SQL Server databsese tables in Access? If you do than you have two choices:

1) Use the "old fashion" ODBC Databases tehnique: first create an ODBC chanel to your SQLServer database (From ODBC Manager in Control panel, or in Administrative Tools if you are using Windows 2000. You can create either a file datasource or a machine datasource). Then you can use this chanel in you link table wizard.

2) Starting with Access 2000, you can have a different type of database: .adp - Microsoft Access Project. This type of "database" allows you to use Access as a front-end to your SQLServer database. This means that you have tables, queries, storeproc in SQL Server and Forms and Reports in Access (all in one single project - .adp) For these kind of project native driversfor SQLServer are used. With Access 2000 you can use SQLServer 7 database, and with Access 2002 (XP) you can use SQLServer 2000 databases.

.Adp are version dependent as you can see from above paragraph. With "link method" you can use any type of SQLServer database you want. The only thing you have to have is the correct version of ODBC drivers for SQLServer. You can download ODBC drivers from microsoft. They are found in a package called "mdac" (Microsoft data access components)

IONUT

PS
As an own opinion it's a very good ideea to migrate your databases to SqlServer, but you should also stop using Access even for a front end. It's very slow with large amounts of data, it has runtime libraries anly from XP version (as much as I know) and therefore is very expensive (you have to have a MS Office licence for each seat). It's true that it is easy to code and it has one of the best report designer Microsoft has ever build, but... that's all

Good luck!|||LOL!! Glad to know there are others in the same situation as me!! I'll check out your posting re the parameters. The replies there may be exactly what I am after.

I've tried the DTS and it works, albiet slowly from Access but getting it to talk to the source software (Jade) is proving the problem. According to the software suppliers, it is the exact same ODBC link as used when importing in to Access but I can't get it work to date. I generally get an MMC.exe error and it 'packs a sad'.

I'll keep you posted on what I learn from here!

Cheers!

Maria

Originally posted by berniev
I'm not much ahead of you and perhaps there's a better way but...

SELECT * FROM OPENROWSET( parameters )

-- OR --

SELECT * FROM table_name1 JOIN OPENROWSET( parameters)

would appear to fit the bill.

Trouble is I can't get the 'parameters' bits figured out! (see my earlier post 'openrowset parameters").

Also DTS (Data Transformatin Services) makes it a snap to import via ODBC etc but is tedious to maintain for anything more than quick fixes.|||Also, have a look at "linked servers" under SQL Sercurity tab.

You still have to either input various parameters, but in my case this worked immediately USING A DSN.

And then
SELECT *
FROM OPENQUERY(linked_server_name, 'SELECT * FROM table_name')
-- works

To run DSN-less is still eluding me, but a reply to my post did lead me to save the DTS as VBscript which gave a heap of info. Problem is that the DTS seem to have its own way of doing things that is different to TSQL. Worse, it uses Microsoft Jet OLEDB 4.0, which SQLServer2000 Books on line says is for Access only! (I thought of you) I am using SQLServer7. Perhaps there's a difference. And all references to connectionproperties seem to refer to DTS programming only.

ODBC Connection SQL Server Error

Hello, my VB app fails to connects to a SQL Server.
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PDC.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfully to the server. But when a connection is tried to be made through app it fail: "Login failed, ... user(null)... Not associated with a trusted SQL Server connection"
Any suggestions ?
Thanks
Arnaldo
Arnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>

ODBC Connection SQL Server Error

Hello, my VB app fails to connects to a SQL Server.
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PD
C.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfu
lly to the server. But when a connection is tried to be made through app it
fail: "Login failed, ... user(null)... Not associated with a trusted SQL Ser
ver connection"
Any suggestions ?
Thanks
ArnaldoArnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>

ODBC connection for client application to SQL Server 2005 Express installed on network computer

Hi All,

I've developed an application that connects to a SQL Server 2005 Express database. I created a DSN to connect to the database through ODBC. Currently, I am testing locally and everything works fine.

I would now like to install my application on another workstation and connect remotely to the database located on my development machine.

The client workstation does not have SQL Server 2005 Express installed on it because I would just like my application to connect remotely by creating the DSN and using ODBC. What I'm missing here are the database drivers. The "SQL Natice Client" is not available on this client workstation. How can I deploy the necessary drivers with my installation file so that I may create the required DSN name using the SQL Native Client driver?

Thanks!
Deployment of the SNAC can be found here:

http://msdn2.microsoft.com/en-us/library/ms131334.aspx

If you don′t use the new features of SQL Server 2005, you can also use the MDAC driver which is compatible with the Pre SQL 2005 features of SQL Server 2005.

My best practice is not to use the DSN rather than using direct connection strings which can be configured in configuration files.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de
|||Thanks for the reply.

I can't seem to find the sqlncli.msi file on my drive. I have the Express edition installed. Is there somewhere else I can find this installer for the SNAC driver?

If not, which version of MDAC do I need, and how would I build my DSN? I agree with using connection strings instead of DSN's, unfortunately that is a decision I'm unable to change.

|||

SNAC: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc
it

Just get the newest MDAC, since it makes no difference if you get 2.7 or 2.8 but getting the newest will keep you away from old bugs :-)

The connectionstrings can be found on www.connectionstring.com (Where I also posted an example for the SNAC one :-) )

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Excellent,

I got it working using MDAC.

Thanks!

ODBC Connect Failed in SQL Job

I am running SQL Server 2000 sp4 in Win Server 2003. I have a DTS

packages which connects to FileMaker 6 files via the ODBC driver

installed with FielMaker.

The DTS packages work correctly when

executed directly. However, when executed from a SQL Server Agent job,

the same DTS packages fail. Always with the same message:

Error: -2147467259 (80004005);
Provider Error: 16394 (400A)
Error string: [FileMaker][ODBC FileMaker Pro driver][FileMaker Pro]Connect failed
Error source: Microsoft OLE DB Provider for ODBC Drivers

Searching

for info on the above message seems to indicate a permissions problem.

However, I am running the jobs with an full administrator account. All

connections and the FielMaker files reside on the one server.

Any help on this would be greatly appreciated.

Thank you.

The error you saw is very general, the message indicated a connection fail, so please provide your connection string, and try to connect to your sql instance by simply use osql.exe, if failed, that means the basic connection did not work on your server, otherwise, the error triggered during data operation, then you need sql profile to track which client operation cause server close connection.

Thanks!

Ming.

ODBC --Call Failed exception in application?

Hi, everyone! I hope I'm putting this in the correct forum... forgive me if I haven't!
I've written a neat little app in Visual C# that connects to an MSAccess 2003 database. Because of the really great functionality of ADO.NET, I was able to circumvent a lot of the concurrent connection limitations of Access by using DataSets - alas, I was only delaying the inevitable transition to SQL Server 2000
Since the internal dataset fills in my C# app are written for OLE, and since I've already configured it to connect to the Access database, I was really hopingthat I could just use a linked table to the exported data on SQL Server. However, when I did just this, I got a "ODBC --Call Failed" unhandled exception in my application when I tried to make a simple data change and save it back to the database - no other descriptive error numbers or anything. It appears to be connecting, as I can navigate records, I just cannot make a single change to them, or add new records.
- The changes I made do not propogate, so the MSKB regarding ODBC and cursors isn't the solution
- I did remember to set a PK when I exported from Access to SQL Server 2000
- It's {most likely?} not a permissions issue; I'm in as Administrator, with the ODBC connection set up to use NT Authentication
- I've got SQL Server 2000 running SP3a as well as the latest version of JET running on my 2k3 Server
Any help would be greatly appreciated!

Hi,

as long as Access doenst have a primry key defined on the table it isn′t able to do an update / insert. Try to open the access database and insert a new row in th linked table, i guess it is greyed. Define a PK on the appriate columns and you′ll be fine.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Jens,
Thanks for the response. Unfortunately, I had already defined the PK, and it's showing up in Access. I can add records/edit changes in the database using the MSAccess UI... it's just when my C# ADO.NET app tries to do connect to the MS Access file that the problems start manifesting.
Any other ideas?
|||

http://support.microsoft.com/?scid=kb;en-us;303257&spid=2509&sid=49

HTH

ODBC --Call Failed exception in application?

Hi, everyone! I hope I'm putting this in the correct forum... forgive me if I haven't!
I've written a neat little app in Visual C# that connects to an MSAccess 2003 database. Because of the really great functionality of ADO.NET, I was able to circumvent a lot of the concurrent connection limitations of Access by using DataSets - alas, I was only delaying the inevitable transition to SQL Server 2000
Since the internal dataset fills in my C# app are written for OLE, and since I've already configured it to connect to the Access database, I was really hopingthat I could just use a linked table to the exported data on SQL Server. However, when I did just this, I got a "ODBC --Call Failed" unhandled exception in my application when I tried to make a simple data change and save it back to the database - no other descriptive error numbers or anything. It appears to be connecting, as I can navigate records, I just cannot make a single change to them, or add new records.
- The changes I made do not propogate, so the MSKB regarding ODBC and cursors isn't the solution
- I did remember to set a PK when I exported from Access to SQL Server 2000
- It's {most likely?} not a permissions issue; I'm in as Administrator, with the ODBC connection set up to use NT Authentication
- I've got SQL Server 2000 running SP3a as well as the latest version of JET running on my 2k3 Server
Any help would be greatly appreciated!

Hi,

as long as Access doenst have a primry key defined on the table it isn′t able to do an update / insert. Try to open the access database and insert a new row in th linked table, i guess it is greyed. Define a PK on the appriate columns and you′ll be fine.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Jens,
Thanks for the response. Unfortunately, I had already defined the PK, and it's showing up in Access. I can add records/edit changes in the database using the MSAccess UI... it's just when my C# ADO.NET app tries to do connect to the MS Access file that the problems start manifesting.
Any other ideas?
|||

http://support.microsoft.com/?scid=kb;en-us;303257&spid=2509&sid=49

HTH