> Dear Users, > > The idea of having non-ODBC backend for SQL Server has been dangling in > my head for some time. > I'd like to roughly discuss this idea, collect your opinions about > interest, how much would you like to have it, technology, etc. > > 1. Do you like this idea? > 2. Is SQL Server Native Client for OLE DB best native approach > (considering it as a replacement for old and rubbish ODBC) > 3. Which (minimal) version of the SQL Server Native Client should we > consider? > 4. Which (minimal) version of SQL Server should we consider/ > 5. ... > > If there is anyone interested in this idea, I'd appreciate any feedback. > > Best regards, >
First of all MS SQL Server is not the server I'm too familiar with or I'm using on daily basis so don't take what I say for granted. However... There actually 3 ways to communicate with SQL Server from C++: - ODBC Driver - OLE DB COM Driver - The "native" DB library. DB-Library ---------- The last one is seems to be not so recommended my Microsoft and they tell us the ODBC is more then fine: http://msdn.microsoft.com/en-us/library/ms811006.aspx Also DB library seems to be badly documented. ODBC ---- ODBC: it seems to be quite common way to connect to SQL Server also it has an advantage that once implementing it (and I know its API is horrible) you get support of many other data-bases out of box and it is also widely deployed and used (Linux, Unix and others) so virtually implementing ODBC you get a connectivity to any database (modulo crappy ODBC drivers) Also you get an advantage - having good ODBC driver you can connect to MS SQL from non-Windows machines including Linux, Mac and others. So IMHO if you want to improve the support of MS SQL Server it would be better and easier to improve an ODBC driver it does not seems to be very hard. OLE DB ------- First of all it is **COM** API. The question is if you really want to get into it? Other then that OLE DB is yet another generic API to connect to general databases + some more features, similarly to what ODBC does. So it may be valuable to have OLE DB API but I don't think it would give an advantage to use it over ODBC if not give more headache - due to COM nature of such API. Also as additional point it would be quite hard to make the code "cross-compiler" i.e. support non-MSVC compilers like gcc, intel or borland as mostly for "sane" use of COM API you would like to use ATL. My $0.02 Artyom ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
