September 10, 2011 at 11:36 am
Comments posted to this topic are about the item Now you ODBC me now you don't
Best wishes,
Phil Factor
September 10, 2011 at 12:07 pm
So OLE DB is going away. Yet you have said nothing about ODBC going away. If I were to set up an ODBC connection to one of my SQL servers OLE DB is just one of the options. If you are not on a flavor of Windows then I hear the OLE DB is the best choice.
As long as ODBC it self is still supported and there is a good driver to use I think that most folks can deal. I have used ODBC drivers for Quick Books, Access (ugh), Clent Access to get at AS?400 data. Fox Pro, SQL, and others.
As long as we have the freedom to get to the data (in a controlled and secure way of course) that is what is needed (IMHSHO). They close one door, we find a window.
Technology changes. Sometimes old ways have run their life course. Celebrate the good times and the life accomplishments with a large glass. Sing some songs and move along. You will be raising one over me soon enough.
ATBCharles Kincaid
September 12, 2011 at 10:12 am
I understand what you're saying about Microsoft's reasons for moving away from OLE DB and back to OBDC. Proprietary to Microsoft or not (of no consequence in a homogenous Microsoft shop), I would really enjoy a secure, encrypted connection protocol that doesn't require other methods.
September 13, 2011 at 12:45 pm
I hope the SQLNCLI contains inside itself both the SQLOLEDB and SQLODBC providers, and it seems Microsoft is going to throw away SQLOLEDB soon, and SQLNCLI will be exclusively based on SQLODBC only.
When you see the list of providers (maybe while creating an SSIS connection or while creating a linked server), you can see two entities named "Microsoft OLE DB provider for SQL server" and "SQL Native client". This used to be a bit confusing for beginners, and so it is better that they take away the first one and retain the second one only.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply