Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Now you ODBC me now you don't Expand / Collapse
Author
Message
Posted Saturday, September 10, 2011 11:36 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Today @ 5:28 AM
Points: 587, Visits: 2,532
Comments posted to this topic are about the item Now you ODBC me now you don't


Best wishes,

Phil Factor
Simple Talk
Post #1172965
Posted Saturday, September 10, 2011 12:07 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, February 6, 2014 12:59 PM
Points: 801, Visits: 1,962
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.


ATB

Charles Kincaid

Post #1172967
Posted Monday, September 12, 2011 10:12 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 14, 2013 3:11 PM
Points: 11, Visits: 83
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.
Post #1173613
Posted Tuesday, September 13, 2011 12:45 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 3, 2013 4:22 AM
Points: 241, Visits: 263
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.
Post #1174440
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse