locked
Native Connection to a new database - Looking for advise RRS feed

  • Question

  • Hi everyone

    I'm seeking orientation. We have developed a new database engine called TeraManager that runs as a complement to SQL Server.
    TeraManager is very much like any other SQL database but is not transactional and is aimed at handling very efficiently large ammounts of records (I mean billions of records per day literally). We have of course standard ODBC connectivity and even a .Net component so the TMGR can be accesed from SQL or other MSFT environments but we are seeking to have a sort of native connection, like the Oracle transparent gateway for instance.

    Can anyone give me a hint where should we start?
    Adrian
    Saturday, October 10, 2009 4:05 PM

Answers

  • Linked servers between two SQL Servers communicate over the OLE DB provider for SQL Server (SQL Server Native Client).  With an ODBC driver, you have to go through the OLE DB provider for ODBC drivers, which has some overhead.  Dan sort of hit the nail on the head when he said "OLE DB provider", because that is probably the best way to get fast, native communication with SQL Server.

    There is a tradeoff, though:
    ODBC drivers can be ported fairly directly to *nix, if you felt the need to do this.
    ODBC drivers are somewhat easier to use.

    OLE DB providers rely on COM and so there are no porting options there.
    OLE DB providers can be more difficult to use in non-OO programs.


    Hope that helps,

    John




    This post is provided 'as is' and confers no express or implied warranties or rights.
    Monday, October 12, 2009 7:41 PM

All replies

  • You might be able to add TeraManager as a linked server if you have an OLE DB provider.  See http://msdn.microsoft.com/en-us/library/ms188279.aspx.
    Dan Guzman, SQL Server MVP, http://weblogs.sqlteam.com/dang/
    Saturday, October 10, 2009 4:16 PM
  • Thanks Dan, but would't that be as performant as a standard ODBC connection?

    we are seeking utmost performance, like when to SQL Servers are connected in native form. WHen dealing with huge ammounts of data, the performance in conection can be an issue relatively heavy.

    We were just wondering if we could connect as other SQL Server, but we do not know if that information is open to the public so we can code our own interfaces for that purpose.

    Advise appreciated.

    Adrian
    Saturday, October 10, 2009 4:41 PM
  • Linked servers between two SQL Servers communicate over the OLE DB provider for SQL Server (SQL Server Native Client).  With an ODBC driver, you have to go through the OLE DB provider for ODBC drivers, which has some overhead.  Dan sort of hit the nail on the head when he said "OLE DB provider", because that is probably the best way to get fast, native communication with SQL Server.

    There is a tradeoff, though:
    ODBC drivers can be ported fairly directly to *nix, if you felt the need to do this.
    ODBC drivers are somewhat easier to use.

    OLE DB providers rely on COM and so there are no porting options there.
    OLE DB providers can be more difficult to use in non-OO programs.


    Hope that helps,

    John




    This post is provided 'as is' and confers no express or implied warranties or rights.
    Monday, October 12, 2009 7:41 PM