This project is read-only.

Using OGDI with SQL Server

Apr 8, 2010 at 6:06 PM

I'm interested in using OGDI with SQL Server. Will this be possible and will it be a massive task to modify or just small changes to the connections?

Apr 8, 2010 at 10:48 PM

Do you mean SQL Azure?  If so, then we are currently evaluating adding support for SQL Azure.

Currently, it wouldn't be trivial to take the OGDI codebase as it is and get it working with SQL Azure.  Depending on what you are looking for, WCF Data Services (formerly known as ADO.NET Data Services) might give you what you need:

Have a look at this video. 

How Do I: Getting Started with ADO.NET Data Services over a Relational Database

The commonality between WCF Data Services and OGDI is OData (  With OGDI, we offer more than just an OData service.  We offer an ISDK, Data Loader, AND an OData service.  Our OData service also has extensions to support returning data as KML for mapping scenarios.  This feature is dependent on our storage design.  You could recreate this approach with SQL Azure (and we plan to), but it is not implemented yet.  There are other things about our service that are a little different than what is provided "out of the box" when you use WCF Data Servcies to build an OData service.  We're working on better documentation and videos to explain some of this.  I hope this answer helps.


Nov 30, 2010 at 5:48 PM


I would like to use OGDI with SQL Server but without using Azure. Is that possible? 

Thank you

Nov 30, 2010 at 6:11 PM

Not out of the box.


Nov 30, 2010 at 9:00 PM

Thank you for the quick reply. I read in the release notes that the interactive SDK  is a "Provider model for data access, enabling clean retargeting to alternative data storage systems, e.g. SQL Azure, SQL Server, etc.". That is why I was asking about using SQL Server.

Nov 30, 2010 at 9:40 PM
Edited Nov 30, 2010 at 9:40 PM

Embaraced to say, this is a bit on of an overstatement. Provider model at present doesn't encapsulate storage access fully. Therefore retargetting to SQL Server, possible to be sure, will not be as clean as swaping one provider for another.


Mar 3, 2011 at 6:59 PM

We're still in active development / early alpha stages, but the Open Data Publisher is a port of OGDI to SQL Server:  We are also allowing consumption of external OData feeds from the web UI portion, though it's only tested with GeoREST so far.  Not really advertising this until we get a live site running as a demo and get a few more of the bug fixes / changes we have planned done.