SQL Native Client x32 or x64?

Question

Post reply

SQL Native Client x32 or x64?

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

Syed Jahanzaib Bin hassan SSChampion Points: 11410 More actions · Answer 1

MetaData should be MS SQL Server 2005 or Later because SQL Server 2000 is not a schema base database

and use this new JDBC driver 2.0 by Microsoft

http://www.microsoft.com/sqlserver/2005/en/us/java-database-connectivity.aspx#performance

Regards,

Syed Jahanzaib Bin Hassan

MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

My Blog

http://www.aureus-salah.com

My Blog
www.aureus-salah.com

Orlando Colamatteo SSC Guru Points: 182279 More actions · Answer 2

I am not sure how you can figure out whether your process is 32 or 64 bit.
I'm thinking it could be as simple as launching Task Manager and examining the process to see if *32 appears in the image name. Thoughts?

No ODBC bridge...sounds cleaner than my idea 😀

I'm not sure I undersand DSN-less connections. I'm a .NET developer and never really worked with JDBC. Our Java developer provided me with the XML file that holds the connection attributes.
<?xml version="1.0" encoding="UTF-8"?>
<datasources>
<local-tx-datasource>
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:sqlserver://server:1433;DatabaseName=DB1;useCursors=true;appName=DefaultDS</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<user-name>user</user-name>
<password>password</password>
<check-valid-connection-sql>SELECT COUNT(*) FROM sysobjects</check-valid-connection-sql>
<background-validation-millis>10000</background-validation-millis>
<metadata>
<type-mapping>MS SQLSERVER2000</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>

DSN-less meaning all the info needed to connect to the DB is within the connection string, i.e. there is no need to set anything up through the ODBC applet. This is the preferred way to make app deployments portable. As a .NET dev myself I take them for granted since that's all I use these days. JDBC easily supports DSN-less connections to SQL Server as well and your Java dev is using them.

If you get your answer from Task Manager then I think you're good to go. I don't think you need to tell JDBC whether you're in 32 or 64 bit. The JDBC driver should just be handed the proper Native client binary depending on the mode the process is running in.

Were you just curious about the mechanics, or are you having a specific problem with your app?

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

Orlando Colamatteo SSC Guru Points: 182279 More actions · Answer 3

Syed Jahanzaib Bin hassan (4/20/2011)

MetaData should be MS SQL Server 2005 or Later because SQL Server 2000 is not a schema base database

and use this new JDBC driver 2.0 by Microsoft

http://www.microsoft.com/sqlserver/2005/en/us/java-database-connectivity.aspx#performance

Regards,

Syed Jahanzaib Bin Hassan

MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

My Blog

http://www.aureus-salah.com[/quote%5D

Or you could try current version 3.0 which supports 2008R2:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a737000d-68d0-4531-b65d-da0f2a735707

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

jallmond Ten Centuries Points: 1181 More actions · Answer 4

Were you just curious about the mechanics, or are you having a specific problem with your app?

I was just curious about the mechanics. Our system engineer is installing the native client for an upcoming deployment and noticed there are 32-bit options under the SQL Configuration Manager. He wanted to ensure he hadn't missed something, and I confess I never really thought about it that much. I just assumed if my OS is x64, I should install the x64 native client and call it a day. Glad to have some light shed on the under-the-hood action.

I am also exclusively DSN-less these days, and I guess I just took that for granted. I was overthinking what you meant by DSN-less. Don't think I have used a system DSN since I was developing in Access. I don't miss that at all!

Thanks,

Jared

jallmond Ten Centuries Points: 1181 More actions · Answer 5

Syed Jahanzaib Bin hassan (4/20/2011)

MetaData should be MS SQL Server 2005 or Later because SQL Server 2000 is not a schema base database

and use this new JDBC driver 2.0 by Microsoft

http://www.microsoft.com/sqlserver/2005/en/us/java-database-connectivity.aspx#performance

Regards,

Syed Jahanzaib Bin Hassan

MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

My Blog

http://www.aureus-salah.com[/quote%5D

We are deploying a JBOSS based application using SQL Server 2008 as the back end, and the vendor explicitly states the values we are using. Additionally, we are using the JDBC 3.0 driver per vendor specification as the application requires a JDBC 4.0 compliant driver running on JDK 5.0.

I don't mean to sound impolite, but the information you posted in this thread is not strictly accurate from a technical perspective. I also don't recall soliciting advice on the JDBC driver version. People post on this forum to get expert responses from the wonderfully knowledgeable folks that frequent this forum, not shots in the dark. I appreciate you trying to be helpful, but if you don't know, perhaps you should refrain from posting.

Someone much smarter than I once said, "During the day I have millions of thoughts; most of them I keep to myself."

Thanks,

Jared