gregglarkin
Legendary Poster
Anybody use SQL Native client on JDE OneWorld XE to access SQL Server 2000? That is a new SQL client that Microsoft introduced to support SQL 2005. It is backward compatible with SQL 2000.
brother_of_karamazov
Legendary Poster
[ QUOTE ]
Anybody use SQL Native client on JDE OneWorld XE to access SQL Server 2000? That is a new SQL client that Microsoft introduced to support SQL 2005. It is backward compatible with SQL 2000.
[/ QUOTE ]
I've never messed with it but happened across this today:
From:
http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone.jsp?doc=8f6092e5ccb27fd98825722800025c39/$FILE/xe-erp8-database-tr.htm#_Requirements_for_SQL
"SQL Server Native Client (SNAC):
Note: Microsoft SQL Server Native Client (SNAC) is supported with SQL 2000 database servers for communication with the enterprise server, deployment server, and Windows Clients. The SQL Server Native Client can be downloaded from the Microsoft web site."
Note: If both SQL Server 2000 and SQL Server 2005 databases are used, the SQL Server Native Client is required instead of the SQL Server 2000 Client.
For SQL2005
Note: Microsoft SQL Server Native Client (SNAC) is required on any machine that will communicate with the database server, for example, the enterprise server, deployment server, and Windows Clients. The SQL Server Native Client can be downloaded from the Microsoft web site."
Anybody use SQL Native client on JDE OneWorld XE to access SQL Server 2000? That is a new SQL client that Microsoft introduced to support SQL 2005. It is backward compatible with SQL 2000.
[/ QUOTE ]
I've never messed with it but happened across this today:
From:
http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone.jsp?doc=8f6092e5ccb27fd98825722800025c39/$FILE/xe-erp8-database-tr.htm#_Requirements_for_SQL
"SQL Server Native Client (SNAC):
Note: Microsoft SQL Server Native Client (SNAC) is supported with SQL 2000 database servers for communication with the enterprise server, deployment server, and Windows Clients. The SQL Server Native Client can be downloaded from the Microsoft web site."
Note: If both SQL Server 2000 and SQL Server 2005 databases are used, the SQL Server Native Client is required instead of the SQL Server 2000 Client.
For SQL2005
Note: Microsoft SQL Server Native Client (SNAC) is required on any machine that will communicate with the database server, for example, the enterprise server, deployment server, and Windows Clients. The SQL Server Native Client can be downloaded from the Microsoft web site."
gregglarkin
Legendary Poster
Thanks Jeff!
We just started playing with it. We had found an incompatibility between Windows 2003 R2/SP2 and SQL 2000 running on a multicore processer. In a nut shell, if Win 2003 R2/SP2 was loaded on a deployment server or a terminal server, it timed out when running very long UBEs, forcing us to down rev to SP1.
My Asian counterpart had a hunch and tried out the new SQL native client with Windows 2003 R2/SP2 on both his Deployment and terminal servers and it worked like a charm.
That will also give us our upgrade path to SQL 2005 (which is the next project). Great news!
Gregg
We just started playing with it. We had found an incompatibility between Windows 2003 R2/SP2 and SQL 2000 running on a multicore processer. In a nut shell, if Win 2003 R2/SP2 was loaded on a deployment server or a terminal server, it timed out when running very long UBEs, forcing us to down rev to SP1.
My Asian counterpart had a hunch and tried out the new SQL native client with Windows 2003 R2/SP2 on both his Deployment and terminal servers and it worked like a charm.
That will also give us our upgrade path to SQL 2005 (which is the next project). Great news!
Gregg
