I am planning our ISV Java applications' conversion to SQL Server 2008. I see that the 1.2 driver will work, but is classified as a "downlevel" client. Is there plan to release a new version of the driver that will be more 2008-capable? If not, what if any restrictions or work-arounds should I be aware of for taking advantage of new 2008 features and data types using the current version of the driver?
One important issue is will I be able to use spatial data types in Java? Both the geometry and geography data types are described as .NET Common Language Runtime (CLR) data types. Does that make it impossible to use from a Java application?
Wes, we are planning to release a JDBC driver that will be SQL 2008 ready sometime after the release of SQL 2008. The current driver will connect to 2008 however, some of the new data types will not be available in their native forms until afromentioned SQL2008 ready driver ships. "Wes Clark" wrote: > I am planning our ISV Java applications' conversion to SQL Server 2008. I > see that the 1.2 driver will work, but is classified as a "downlevel" client. > Is there plan to release a new version of the driver that will be more > 2008-capable? If not, what if any restrictions or work-arounds should I be > aware of for taking advantage of new 2008 features and data types using the > current version of the driver?
Currently you can only get the spatial types as binary with our jdbc driver. We are looking into ways of doing this. We may in a future release provide a way to do this. I will ping you if there is a way to do this with the current driver. "Wes Clark" wrote: > One important issue is will I be able to use spatial data types in Java? > Both the geometry and geography data types are described as .NET Common > Language Runtime (CLR) data types. Does that make it impossible to use from > a Java application?
Microsoft's failure to integrate the release plans for a new version of SQL Server 2008 with a new version of the JDBC driver will necessarily delay our ability to take advantage of these new features. How about the new date and time datatypes: DATE, TIME, DATETIMEOFFSET and DATETIME2? Will these be handled by the current driver? If so, how? Perhaps a web page could be created to cover all these issues.
The same question for me, where and when can we receive the jars for new version of JDBC driver --Tony "Wes Clark" wrote: > Microsoft's failure to integrate the release plans for a new version of SQL > Server 2008 with a new version of the JDBC driver will necessarily delay our > ability to take advantage of these new features. > > How about the new date and time datatypes: DATE, TIME, DATETIMEOFFSET and > DATETIME2? Will these be handled by the current driver? If so, how? > > Perhaps a web page could be created to cover all these issues.
Wes, we will try to put a blog about handling the new Katmai data types with the JDBC driver. "Wes Clark" wrote: > Microsoft's failure to integrate the release plans for a new version of SQL > Server 2008 with a new version of the JDBC driver will necessarily delay our > ability to take advantage of these new features. > > How about the new date and time datatypes: DATE, TIME, DATETIMEOFFSET and > DATETIME2? Will these be handled by the current driver? If so, how? > > Perhaps a web page could be created to cover all these issues.
I see the RTM version is now available. What is the latest update on the availability of a new version of the JDBC driver, capable of handling the new date/time and spatial datatypes? "Mugunthan Mugundan" wrote: > Wes, we will try to put a blog about handling the new Katmai data types with > the JDBC driver. > > > "Wes Clark" wrote: > > > Microsoft's failure to integrate the release plans for a new version of SQL > > Server 2008 with a new version of the JDBC driver will necessarily delay our > > ability to take advantage of these new features. > > > > How about the new date and time datatypes: DATE, TIME, DATETIMEOFFSET and > > DATETIME2? Will these be handled by the current driver? If so, how? > > > > Perhaps a web page could be created to cover all these issues.
Hi Wes, The existing Microsoft SQL Server JDBC driver v1.2 supports connecting to SQL Server 2008 as a down level client. The new date, time, datetime2, and datetimeOffset data types are sent back from SQL Server as a String to maintain full precision when compared to SQL Server's datetime data type. We will be supporting SQL Server 2008 data types natively in a future release of the driver. Jimmy
For our ISV planning for support of SQL Server 2008 and all the new data types, I would like to have some idea of a schedule for when the new version of the JDBC driver will be available. "Jimmy Wu" wrote: > Hi Wes, > > The existing Microsoft SQL Server JDBC driver v1.2 supports connecting to > SQL Server 2008 as a down level client. The new date, time, datetime2, and > datetimeOffset data types are sent back from SQL Server as a String to > maintain full precision when compared to SQL Server's datetime data type. > We will be supporting SQL Server 2008 data types natively in a future > release of the driver. > > Jimmy > >
Are there any news about Geometry support in the JDBC driver? Can you give a schedule when the next JDBC driver version with Geometry support will be released? Or have you any hints about how to determine if the read value is a Geometry-Type or anything else? Thanks a lot, Pascal "Mugunthan Mugundan[MSFT]" wrote: > Currently you can only get the spatial types as binary with our jdbc driver. > We are looking into ways of doing this. We may in a future release provide a > way to do this. I will ping you if there is a way to do this with the current > driver. > > "Wes Clark" wrote: > > > One important issue is will I be able to use spatial data types in Java? > > Both the geometry and geography data types are described as .NET Common > > Language Runtime (CLR) data types. Does that make it impossible to use from > > a Java application?
