MS SQL vs Versant DB

Is anyone familiar with Versant and how it stacks up against MS SQL as a
development technology. I have a client that currently has an application
developed on Versant and they want to investigate moving to MS SQL.
Any help or direction is appreciated.
Thanks
--
George AdrianAs far as I can tell from a quick look at their web site, the Versant DB
does not use SQL, but instead is queried via an object API. Is that
accurate? If so, the changes to the application's data access code are
going to be massive -- you're going to have to write queries instead of
using objects. I hope that the client's code is well structured and that
they've segregated the data access and business / user interface code enough
that this won't require a complete re-write of the application.
Why do they want to switch, anyway?
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
news:EEEC9583-E662-4612-9071-001CDE36CF57@.microsoft.com...
> Is anyone familiar with Versant and how it stacks up against MS SQL as a
> development technology. I have a client that currently has an application
> developed on Versant and they want to investigate moving to MS SQL.
> Any help or direction is appreciated.
> Thanks
> --
> George Adrian|||Adam,
thanks for your feedback, yes the database is an object database.
The client wishes to change because the development is costing too much and
the developer is unable to provide any documentation. The community for
development in this field seems to be smaller and therefore more expensive.
that is why they want to change.
--
George Adrian
"Adam Machanic" wrote:

> As far as I can tell from a quick look at their web site, the Versant DB
> does not use SQL, but instead is queried via an object API. Is that
> accurate? If so, the changes to the application's data access code are
> going to be massive -- you're going to have to write queries instead of
> using objects. I hope that the client's code is well structured and that
> they've segregated the data access and business / user interface code enou
gh
> that this won't require a complete re-write of the application.
> Why do they want to switch, anyway?
>
> --
> Adam Machanic
> Pro SQL Server 2005, available now
> http://www.apress.com/book/bookDisplay.html?bID=457
> --
>
> "George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
> news:EEEC9583-E662-4612-9071-001CDE36CF57@.microsoft.com...
>
>