November 5, 2016 at 12:05 am
Comments posted to this topic are about the item I can ODBC clearly now
Best wishes,
Phil Factor
November 5, 2016 at 9:20 am
ODBC as a protocol has saved me time after time. Client has some weird data store based on MUMPS? ODBC for the win!
November 5, 2016 at 11:35 am
MUMPS? Good grief, that is an amazing survival. I wrestled that fiendish system in the eighties. It is true, though. If you curl up your nose at something you have to get data from, the chances are that ODBC will protect you from it.
Best wishes,
Phil Factor
November 5, 2016 at 11:44 am
Hear, Hear!
November 7, 2016 at 3:54 am
ODBC, perhaps, is one of Microsoft's greatest technical design successes. I never understood the driver (no pun intended) for Microsoft so keep reinventing the wheel.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 7, 2016 at 6:01 am
Microsoft is a bit of a funny company. It has shaped so much of my career and yet it seems adept at shooting itself in the foot.
ODBC as the example here where they treat their good idea with tepid enthusiasm.
Try Outlook on a Mac. All the good bits you've taken for granted since the turn of the Millenium? It's on their TODO list.
Why does each release of Visio get less feature rich in the database department. Remember Visio pre-2000 could reverse AND FORWARD engineer!
November 7, 2016 at 8:50 am
Do you have any links for people working through examples of this that are particularly instructive?
It there a longer intro to the subject somewhere?
Thanks!
412-977-3526 call/text
November 7, 2016 at 11:10 am
Lukewarm support for ODBC? But Microsoft keeps stated the following back in 2011 and keep repeating it.
ODBC is the de-facto industry standard for native relational data access, which is supported on all platforms including SQL Azure.
The commercial release of Microsoft SQL Server, codename “Denali,” (2012) will be the last release to support OLE DB.
We encourage you to adopt ODBC in the development of your new and future versions of your application.
:Whistling:
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
November 7, 2016 at 12:18 pm
@eric So why no ODBC for DocumentDB so far?
That announcement startled everyone in fact, it turned out that this announcement was only about the deprecation of Microsoft SQL Server OLE DB provider. It didn't affect other Microsoft SQL Server features and products that are built on top of OLE DB or use OLE DB, like Distributed Query (Linked Server), SQL Server Integration Services, SQL Server Analysis Services. As far as I can see, it represents no general policy direction because too much code is involved, and we'd probably need changes to the ODBC spec to allow it to replace OLEDB effectively.
Best wishes,
Phil Factor
November 7, 2016 at 1:33 pm
Phil Factor (11/7/2016)
@eric So why no ODBC for DocumentDB so far?That announcement startled everyone in fact, it turned out that this announcement was only about the deprecation of Microsoft SQL Server OLE DB provider. It didn't affect other Microsoft SQL Server features and products that are built on top of OLE DB or use OLE DB, like Distributed Query (Linked Server), SQL Server Integration Services, SQL Server Analysis Services. As far as I can see, it represents no general policy direction because too much code is involved, and we'd probably need changes to the ODBC spec to allow it to replace OLEDB effectively.
ODBC is geared toward tabular (relational, flat files, XML) resultsets isn't it? It doesn't support binary objects or document like JSON and DIF?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
November 7, 2016 at 4:16 pm
There are several JSON and XML ODBC drivers being sold. There has to be some mapping of the JSON documents to tables. You generally use XML-based schema configuration files to define these tables. Some try to figure out rows and tables from the documents but the results aren't always pretty.
Best wishes,
Phil Factor
November 8, 2016 at 7:35 am
Is this a fair overview of the technology?
https://en.wikipedia.org/wiki/Open_Database_Connectivity
412-977-3526 call/text
November 8, 2016 at 9:56 am
To Robert Sterbal: I would say yes, this is a reasonable overview. Key concept is "translation" of dbms commands.
November 10, 2016 at 5:32 am
Phil Factor (11/5/2016)
MUMPS? Good grief, that is an amazing survival. I wrestled that fiendish system in the eighties. It is true, though. If you curl up your nose at something you have to get data from, the chances are that ODBC will protect you from it.
MUMPs, or M technology is still about. As well as the likes of Meditech, VistA in the US and other healthcare system providers, your market leading Object Oriented Big Data, spanking new advanced techxnology with many many buzzwords, Cache database is based on Mumps under the bells and whistles on the hood.
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
November 10, 2016 at 7:49 am
Phil Factor (11/5/2016)
MUMPS? Good grief, that is an amazing survival. I wrestled that fiendish system in the eighties. It is true, though. If you curl up your nose at something you have to get data from, the chances are that ODBC will protect you from it.
It's called Caché now days and as the designated Data Janitor/Data Sewage Tech at the company, I had to do the ETL code to bring it's fruits into our products. As a reward I still get to maintain it. 😛
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply