64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
[url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[/u
rl]
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:

> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> [url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[
/url]
> That should get things in working order.
> Jesse
>

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> > The server is IBM XS 466.
> > The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> > (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> > Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> > 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> > oracle.msbut I can find some drivers about oracle in ODBC,but must run
> > 'c:\windows\system32\odbcad32.exe'
> > This proble puzzle me for some days
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>

64 bit vs 32 bit with same RAM.

If I’m setting up a server, and I don’t plan on putting a lot of RAM(4GB
maybe 8GB) in it, will 64bit still be better?
thanks
If I'm to make a choice in the specific situation that you described and my
databases have always been on the 32-bit platform, I would most likely just
leave them on 32-bit until I run tests to determine if there is any benefits
going to 64 bit at all.
But there is always this issue of 'scaling forward' to take advantage of
what's coming in computing, and 64-bit generally speaking would put you in a
better position to scale forward. Of course, for your particular app, scaling
forward may or may not be relevant.
Now, note that 64-bit does carry some overhead in terms of larger data
structures and so on. Not all workloads will automatically benefit
performance wise from moving to 64-bit. For instance, if the data set of your
workloads can fit largely in memory, you may find 32-bit faster than 64-bit.
Linchi
"Jason" wrote:

> If I’m setting up a server, and I don’t plan on putting a lot of RAM(4GB
> maybe 8GB) in it, will 64bit still be better?
> thanks

64 bit vs 32 bit with same RAM.

If Iâ'm setting up a server, and I donâ't plan on putting a lot of RAM(4GB
maybe 8GB) in it, will 64bit still be better?
thanksIf I'm to make a choice in the specific situation that you described and my
databases have always been on the 32-bit platform, I would most likely just
leave them on 32-bit until I run tests to determine if there is any benefits
going to 64 bit at all.
But there is always this issue of 'scaling forward' to take advantage of
what's coming in computing, and 64-bit generally speaking would put you in a
better position to scale forward. Of course, for your particular app, scaling
forward may or may not be relevant.
Now, note that 64-bit does carry some overhead in terms of larger data
structures and so on. Not all workloads will automatically benefit
performance wise from moving to 64-bit. For instance, if the data set of your
workloads can fit largely in memory, you may find 32-bit faster than 64-bit.
Linchi
"Jason" wrote:
> If Iâ'm setting up a server, and I donâ't plan on putting a lot of RAM(4GB
> maybe 8GB) in it, will 64bit still be better?
> thanks

64 bit TextFile ConnectionString unable to dynamically change?

Hello,

On a 64bit Itanium cluster, I'm having a problem dynamically setting the ConnectionString of a TextFile Source using the "EvaluateAsExpression" = True and setting the ConnectionString using an expression from a variable. I get the error message:

-1073647612,0x,The result of the expression "@.[User::vFullFilePath]" on property "ConnectionString" cannot be written to the property. The expression was evaluated, but cannot be set on the property.

This is not a problem at all on a 32bit machine. I can run the same package on 32bit and it runs fine.

The funny thing is, I'm able to dynamically change the ConnectionString of a Logfile that we're writing all of the errors to, which I believe is using a TextFile Destination connection under the covers somehow (I'm using the SSIS Logging, to a textfile).

Can anyone confirm if this is a problem in 64bit?

Thanks,

Andy

It just dawned on me that this may be due to the fact that I'm using "LocalHost" as a servername rather than my cluster name when I set up the UNC Path. I'll change that and see if it runs. I'm guessing that has to be the problem. Silly me.

64 Bit Subscriber Compability

I am going to buy 2 new 4 way 64 bit boxes and i was wondering if they are
going to be compatible for my current 32bit transactional replication.
In other words they are going to become subscribers of my current
replication. I read an article on microsoft that said that 64bit SQL
Replication will not work if the subscriber is a 32bit Edition of SQL, so i
am wondering if it will work the other way around.
Thank you,
Yovan Fernandez
My understanding is that it will work. Where is this article you are
referring to?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Yovan Fernandez" <YovanFernandez@.discussions.microsoft.com> wrote in
message news:54D866E8-BBF4-4799-8224-1CC3B7F7AB07@.microsoft.com...
> I am going to buy 2 new 4 way 64 bit boxes and i was wondering if they
are
> going to be compatible for my current 32bit transactional replication.
> In other words they are going to become subscribers of my current
> replication. I read an article on microsoft that said that 64bit SQL
> Replication will not work if the subscriber is a 32bit Edition of SQL, so
i
> am wondering if it will work the other way around.
> --
> Thank you,
> Yovan Fernandez

64 Bit SQL Server try to access 32-Bit

Hi All,

I have a scenario where today we are migrating the existing code to new production server which is 64 Bit server.

The SSIS packages are put on new server and we are trying to run.

I tried to run a simple select query to fetch data from a 32bit remote server from cmd prompt usings a .sql file and it gives me error.

But this is the known issue of

‘a 64-bit SQL server trying to communicate to a 32-bit sql server’ and the error message is

The error message is similar to the following:

The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.
Msg 7311, Level 16, State 2, Line 1
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "<LinkedServerName>". The provider supports the interface, but returns a failure code when it is used

I saw the help for this in support.microsoft and it is suggested the resolution is

‘To resolve this problem, install SQL Server 2000 SP3 or SQL Server 2000 SP4 on the 32-bit SQL Server 2000 server. Then, manually run the Instcat.sql script that is included with SQL Server 2000 SP3 or SP4 on the 32-bit SQL Server 2000 server.’

I cannot do this as the remote server which am trying to access is not under my control and other issues.

Please suggest me what is the work around and what modifications do I need to do for my SSIS packages?

Help much appreciated.

Thanks and Regards

Sai

Hello,

I’ve just had the same problem. I was trying to access a SQL2K from a SQL2K5 64bits server. Although I had it a as a linked server, I had the same error.

Reading information, I found the patch to solve this problem here

http://support.microsoft.com/kb/906954

But, maybe if you don’t have the SQL2K server under your control, you won’t be able to execute the patch.

There is another way to make this, using OPENQUERY

select * from openquery([RemoteServer],'select * from DB.dbo.table')

And you won’t have the error. I tried it before install the patch and it worked for me.

Krgrds