Subject:Is it possible to add new database types to Stylus Studio? Author:(Deleted User) Date:24 May 2007 02:23 PM
I am assuming that Microsoft SQL Server 2000 is treated differently from Microsoft SQL Server 2005 (and 2005 Express), and also that the Microsoft SQL Server 2005 Compact Edition (CE) will require yet another Java driver for Stylus Studio.
Is that right?
If so, how can they be added to Stylus Studio 2007?
Subject:Is it possible to add new database types to Stylus Studio? Author:Minollo I. Date:24 May 2007 02:31 PM
You don't need different/additional drivers when connecting to any of the supported database versions (see http://www.xquery.com/relational/ for full details). We don't test "Compact Edition"; but I wouldn't be surprised if it just worked.
Currently, you can only rely on the set of databases and drivers officially supported by DataDirect XQuery.
Subject:Is it possible to add new database types to Stylus Studio? Author:(Deleted User) Date:24 May 2007 08:33 PM Originally Posted: 24 May 2007 08:22 PM
OK, thanks. I will try out the CE as soon as I get my Microsoft SQL Server 2005 Express SP1 to work!
I'm also glad to see that Oracle 10 is supported.
I would assume that includes the free 10g Express(XE) edition, which is commonly used in GIS (spatial data mapping) these days.
Subject:Is it possible to add new database types to Stylus Studio? Author:(Deleted User) Date:24 May 2007 10:41 PM Originally Posted: 24 May 2007 10:40 PM
OK. The way we use Oracle XE does use spatial types but does that through the Oracle simplified spatial API (?Locator), and that code has been written by a GIS vender (Manifold Systems GIS).
<off topic>
That's not my primary concern though; I need to round-trip XML to a RDBMS where the required conformance is to a series of XML Schemas - ISO19139.
</>
Subject:Is it possible to add new database types to Stylus Studio? Author:(Deleted User) Date:25 May 2007 10:28 PM
For Microsoft SQL Server 2005 Express edition, what Stylus Studio Support has instructed me to use (and it works) is a significantly different URL string, for Windows Authentication connection -
//localhost\SQLEXPRESS;AuthenticationMethod=Type2
and for user-name - just a space (leaving the password blank).
I suspect that the
;AuthenticationMethod=Type2
can be used for SQL Server 2005 (other versions than Express) when Windows Authentication is used - rather than the Port 1433 that the URL defaults to.
I will be interested to know the correct connect string (URL) for Microsoft SQL Server 2005 CE (Compact Edition).