Tuesday, February 14, 2012

dblib support in SQL 2005?

Hi there,

We have a server application that's built on DBLIB. From what I can tell, it runs on SQL2005, but I'm looking for official confirmation that it's supported. I recall seeing a document recently that said it was supported, but that there would be no documentation released for the API set any longer.

Anyone have any links to official information?

Thanks.

The following is copied from an internal email. It should answer your question. I have no official link for this except http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dblibc/dbc_pdc00b_589v.asp


Just to answer any lingering questions.
- ntwdblib.dll never shipped with the OS.
- ntwdblib.dll did ship with SQLServer up through SQLServer 2005. It is now deprecated.
- sqlserver 2005 supports down level to three versions. So you can use a dblib (ntwdblid.dll) based application to connect to sqlserver 2005.
- ntwdblib.dll never shipped a 64bit version.
Please make sure the ISV understands that they should be actively porting this application over to odbc or oledb.

|||

Here is the official doc.

http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx

Although the SQL Server 2005 Database Engine still supports connections from existing applications using the DB-Library and Embedded SQL APIs, it does not include the files or documentation needed to do programming work on applications that use these APIs. A future version of the SQL Server Database Engine will drop support for connections from DB-Library or Embedded SQL applications. Do not use DB-Library or Embedded SQL to develop new applications. Remove any dependencies on either DB-Library or Embedded SQL when modifying existing applications. Instead of these APIs, use the SQLClient namespace or an API such as OLE DB or ODBC. SQL Server 2005 does not include the DB-Library DLL required to run these applications. To run DB-Library or Embedded SQL applications you must have available the DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server 2000.

No comments:

Post a Comment