We have a legacy Java application that we maintain in Visual J++; we are
moving to SQL Server 2005 and would like to switch it from an old WebLogic
JDBC driver to the new Microsoft SQL Server 2005 JDBC Driver.
However, we're noticing strange behavior with regard to instantiating the
"com.microsoft.sqlserver.jdbc.SQLServerDriver" class (no class def found
errors even though the sqljdbc.jar file is specified on the correct path in
the Classpath environment variable, and using FileMon we can see the app
finding the file).
I assume this means that we're running under the old, and unsupported,
Microsoft Java VM. Is it possible this VM does not support the new JDBC
driver?
Steven Bras
Tessitura Network, Inc.
Hi Steven,
Thank you for posting.
Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
it dosn't support new built java components. I suggest you tried testing
the JDBC driver through standard SUN J2SE SDK to see whether it works. For
VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Thanks for your response; can you point me to samples of how to use ole db in
java?
Steven Bras
Tessitura Network, Inc.
"Steven Cheng[MSFT]" wrote:
> Hi Steven,
> Thank you for posting.
> Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
> J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
> it dosn't support new built java components. I suggest you tried testing
> the JDBC driver through standard SUN J2SE SDK to see whether it works. For
> VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ==================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
|||Thanks for your response Steven,
I'm not quite sure about a complete example on connecting database through
OLEDB provider in VJ++, I think it'll be better to post in some VJ++ or
data accessing specific newsgroup. Also, have you any plan on migrating the
program to pure .net framework so that we have more choice on data
accessing to SQL Server?
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Showing posts with label java. Show all posts
Showing posts with label java. Show all posts
Friday, March 23, 2012
New SQL Server 2005 JDBC 1.0 & Visual J++
We have a legacy Java application that we maintain in Visual J++; we are
moving to SQL Server 2005 and would like to switch it from an old WebLogic
JDBC driver to the new Microsoft SQL Server 2005 JDBC Driver.
However, we're noticing strange behavior with regard to instantiating the
"com.microsoft.sqlserver.jdbc.SQLServerDriver" class (no class def found
errors even though the sqljdbc.jar file is specified on the correct path in
the Classpath environment variable, and using FileMon we can see the app
finding the file).
I assume this means that we're running under the old, and unsupported,
Microsoft Java VM. Is it possible this VM does not support the new JDBC
driver?
Steven Bras
Tessitura Network, Inc.Hi Steven,
Thank you for posting.
Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
it dosn't support new built Java components. I suggest you tried testing
the JDBC driver through standard SUN J2SE SDK to see whether it works. For
VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thanks for your response; can you point me to samples of how to use ole db i
n
java?
--
Steven Bras
Tessitura Network, Inc.
"Steven Cheng[MSFT]" wrote:
> Hi Steven,
> Thank you for posting.
> Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
> J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, s
o
> it dosn't support new built Java components. I suggest you tried testing
> the JDBC driver through standard SUN J2SE SDK to see whether it works. For
> VJ++ we may consider using the OLEDB COM interface to access the SQL Serve
r.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>|||Thanks for your response Steven,
I'm not quite sure about a complete example on connecting database through
OLEDB provider in VJ++, I think it'll be better to post in some VJ++ or
data accessing specific newsgroup. Also, have you any plan on migrating the
program to pure .net framework so that we have more choice on data
accessing to SQL Server?
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
moving to SQL Server 2005 and would like to switch it from an old WebLogic
JDBC driver to the new Microsoft SQL Server 2005 JDBC Driver.
However, we're noticing strange behavior with regard to instantiating the
"com.microsoft.sqlserver.jdbc.SQLServerDriver" class (no class def found
errors even though the sqljdbc.jar file is specified on the correct path in
the Classpath environment variable, and using FileMon we can see the app
finding the file).
I assume this means that we're running under the old, and unsupported,
Microsoft Java VM. Is it possible this VM does not support the new JDBC
driver?
Steven Bras
Tessitura Network, Inc.Hi Steven,
Thank you for posting.
Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
it dosn't support new built Java components. I suggest you tried testing
the JDBC driver through standard SUN J2SE SDK to see whether it works. For
VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thanks for your response; can you point me to samples of how to use ole db i
n
java?
--
Steven Bras
Tessitura Network, Inc.
"Steven Cheng[MSFT]" wrote:
> Hi Steven,
> Thank you for posting.
> Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
> J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, s
o
> it dosn't support new built Java components. I suggest you tried testing
> the JDBC driver through standard SUN J2SE SDK to see whether it works. For
> VJ++ we may consider using the OLEDB COM interface to access the SQL Serve
r.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>|||Thanks for your response Steven,
I'm not quite sure about a complete example on connecting database through
OLEDB provider in VJ++, I think it'll be better to post in some VJ++ or
data accessing specific newsgroup. Also, have you any plan on migrating the
program to pure .net framework so that we have more choice on data
accessing to SQL Server?
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Friday, March 9, 2012
New Java Driver spec
Will the future Java driver feature the full JDBC 4.0 specification?
When and how can we start participating with beta,pre-beta testing?Hi,
I heared that there will be a public beta late summer.|||The SQL Server 2005 driver will be a JDBC 3.0 spec level driver. The 4.0 spec is still in review and final release dates are still not set. We plan to move to 4.0 as soon as it is practical.
When and how can we start participating with beta,pre-beta testing?Hi,
I heared that there will be a public beta late summer.|||The SQL Server 2005 driver will be a JDBC 3.0 spec level driver. The 4.0 spec is still in review and final release dates are still not set. We plan to move to 4.0 as soon as it is practical.
Re: public beta -- it will be announced sooner rather than later.
-shelby|||But the final specs are expected in a month, don't you think there is time to implement it before final release? Anyhow, even if at first it's 3.0 could you speculate on how long would it take to implemet the 4.0 specs?|||Implementing the 4.0 spec will be non-trivial. Even though the spec is in final review, the spec will not be available until the Java SE 6.0 (Mustang) release, which looks like the fall of '06 -- another year.
The Microsoft SQL Server 2005 JDBC Driver v1.0 will be 3.0 spec, but we plan to move to the 4.0 spec in a year when it is practical.
-shelby
New Java Driver spec
Will the future Java driver feature the full JDBC 4.0 specification?
When and how can we start participating with beta,pre-beta testing?Hi,
I heared that there will be a public beta late summer.|||The SQL Server 2005 driver will be a JDBC 3.0 spec level driver. The 4.0 spec is still in review and final release dates are still not set. We plan to move to 4.0 as soon as it is practical.
When and how can we start participating with beta,pre-beta testing?Hi,
I heared that there will be a public beta late summer.|||The SQL Server 2005 driver will be a JDBC 3.0 spec level driver. The 4.0 spec is still in review and final release dates are still not set. We plan to move to 4.0 as soon as it is practical.
Re: public beta -- it will be announced sooner rather than later.
-shelby|||But the final specs are expected in a month, don't you think there is time to implement it before final release? Anyhow, even if at first it's 3.0 could you speculate on how long would it take to implemet the 4.0 specs?|||Implementing the 4.0 spec will be non-trivial. Even though the spec is in final review, the spec will not be available until the Java SE 6.0 (Mustang) release, which looks like the fall of '06 -- another year.
The Microsoft SQL Server 2005 JDBC Driver v1.0 will be 3.0 spec, but we plan to move to the 4.0 spec in a year when it is practical.
-shelby
New Java driver for SqlServer
Theres been rumors on a future effort in building a new JDBC driver to support the SqlServer 2k5. What level of JDBC will it strive to accomplish? Can it be a more open project? Also, the old driver perhaps lacks some things that higher JDBC specs feature so it would be nice if it could provide some sort of backward compatibility.
It would be nice to have the new RowSet thingies and some generics support.Hi schrepfler,
It would be nice to have the new RowSet thingies and some generics support.Hi schrepfler,
where can I get that old jdbc driver from? and did you use it with 2005 ?|||The old driver (latest version is SP3) can be found here. It's not a bad driver but it's old in architecture and should be updated. I haven't tried it with 2k5 as it is said it's not compatible plus I haven't installed sqlserver 2k5 yet (having problems in installation procedure).|||Thank you!!|||The best place to ask this is the Data Access forum, but we are working on the new driver so now is the time to give the feedback.
-Euan|||I thought first we have a alpha or beta product then we give feedback?|||You can wait but the earlier we get the feedback the better|||Ok, you convinced me, you want me to go to the DataAccess forum and ask what I want in the driver?|||Can I get a beta of the new Driver? I'm developing a CMS using a MySQL Database and would like to see if SQL Server 2005 is more powerful.|||Yep please do, we want all the input we can get.
-Euan
Subscribe to:
Posts (Atom)