Login or Sign Up to become a member!
LessThanDot Sit Logo

LessThanDot

Data Management

Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.

LTD Social Sitings

Lessthandot twitter Lessthandot Linkedin Lessthandot friendfeed Lessthandot facebook Lessthandot rss

Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.

Your profile

    Search

    XML Feeds

    Google Ads

    « Watch Me (and 23 Others!) During 24 Hours of PASS: Summit PreviewReporting Services Error: “The tablix has a detail member with inner members” (And How To Fix It) »
    comments

    According to the Microsoft SQLNCli team blog, SQL Server, codename "Denali", will be the last release to support OLE DB.

    Here is what they are currently saying

    The next release of Microsoft SQL Server, codename “Denali”, will be the last release to support OLE DB. OLE DB will be supported for 7 years from launch, the life of Denali support, to allow you a large window of opportunity for changing your applications before the deprecation. This deprecation applies to the Microsoft SQL Server OLE DB provider only. Other OLE DB providers as well as the OLE DB standard will continue to be supported until explicitly announced.

    We encourage you to adopt ODBC in the development of your new and future versions of your application. You don’t need to change your existing applications using OLE DB, as they will continue to be supported for seven years from the launch of Denali, but you may want to consider migrating those applications to ODBC as a part of your future roadmap.

    And

    ODBC is the de-facto industry standard for native relational data access, which is supported on all platforms including SQL Azure. Cloud is universal and in order to support all client applications connecting from any platform to the cloud, Microsoft has been fully aligned with ODBC on SQL Azure, as ODBC is the only set of APIs that are available on all platforms including non-Windows platforms.

    Mmmm..it looks like ODBC is back from the dead.......

    What do you think...how will this impact you? Leave a comment if this affects you or if you have been using ODBC all along

    More details including information on how to migrate your applications can be found here: http://blogs.msdn.com/b/sqlnativeclient/archive/2011/08/29/microsoft-is-aligning-with-odbc-for-native-relational-data-access.aspx

    About the Author

    User bio imageDenis has been working with SQL Server since version 6.5. Although he worked as an ASP/JSP/ColdFusion developer before the dot com bust, he has been working exclusively as a database developer/architect since 2002. In addition to English, Denis is also fluent in Croatian and Dutch, but he can curse in many other languages and dialects (just ask the SQL optimizer) He lives in Princeton, NJ with his wife and three kids.
    Social SitingsTwitterFacebookLinkedInHomePageFlickrLTD RSS Feed
    1140 views
    Instapaper

    4 comments

    Comment from: Craig [Visitor]
    Craig Good riddance.
    Maybe this will finally help convince my company to stop developing for OLE DB and move on to ODBC. While Denali looks good, I am already excited for post-Denali.

    However, since Microsoft says that they will continue to support it for another 7 years, I am sure that my company will wait exactly 7 years to change...
    08/30/11 @ 13:24
    Comment from: Naomi Nosonovsky [Member]
    Naomi Nosonovsky Well, VFP had been 'killed' a while ago. Anyway, if they plan to kill Ole DB I doubt they will produce a new ODBC for VFP... The last ODBC driver for VFP supports VFP6.0 only, so it doesn't support many new features that came into VFP after that.

    08/30/11 @ 21:36
    Comment from: Alex Ullrich [Member] Email
    Alex Ullrich We typically use ODBC where we can't use SqlClient / OracleClient. It will be nice to have a real standard in the future I suppose.
    09/01/11 @ 08:29
    Comment from: genomon [Member]
    genomon Is this the same Microsoft that reccomended using the OLEDB provider when connecting to SQL Server from Office apps such as Access? The (Evil) Empire Strikes Back...
    09/01/11 @ 09:09

    Leave a comment


    Your email address will not be revealed on this site.

    Your URL will be displayed.
    (Line breaks become <br />)
    (Name, email & website)
    (Allow users to contact you through a message form (your email will not be revealed.)