<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE product SYSTEM "bag-1.0.dtd" >
<product shortname="tsqlquery">
   <name>SQLQuery</name>
   <vendor>Component Store Ltd</vendor>
   <currentversion>2.4.1</currentversion>
   <wikiname>SqlQuery</wikiname>
   <web>http://www.component-store.com</web>
   <email>info@component-store.com</email>
   <internalemail>thomas@component-store.com</internalemail>
   <shortdescription>a TDataset-descendant component to access MS SQL
   Server through the DBLIB API</shortdescription>
   <sourceavailable>1</sourceavailable>
   <dataaware>TDataSet (D3+)</dataaware>
   <querylanguage></querylanguage>
   <delphivers>3 4 5</delphivers>
   <cppbvers>3 4</cppbvers>
   <deployment>TSQLQuery compiles into the EXE. It requires the SQL
   Server DB-LIB; specifically ntwdblib.dll</deployment>
   <models>
      <local primary="0"></local>
      <fileserver primary="0"></fileserver>
      <clientserver primary="1">Yes</clientserver>
      <webserver primary="0"></webserver>
   </models>
   <packages>
      <package description="1 developer license" price="$249" />
      <package description="5 developer license" price="$649" />
      <package description="10 developer license" price="$1199" />
      <package description="Site License, with source"
      price="$2900" />
   </packages>
   <compatibility>
      <tool name="(Delphi) Database Explorer" compatible="Unknown" />
      <tool name="Ace Reporter" compatible="Yes" />
      <tool name="InfoPower" compatible="Yes" />
      <tool name="Orpheus (TurboPower)" compatible="Unknown" />
      <tool name="QuickReports" compatible="Unknown" />
      <tool name="RAVE Reports" compatible="Unknown" />
      <tool name="ReportBuilder Pro" compatible="Unknown" />
   </compatibility>
   <dataformats>
      <dataformat database="Microsoft SQL Server" native="1" via=""
      notes="TSQLQuery uses DB-LIB, the older native SQL Server library. ODBC is also now considered a native interface to SQL Server." />
   </dataformats>
   <vendordescription>
      <h4>Summary</h4>
      <ul>
         <li>TDataSet descendant (use all database-controls)</li>
         <li>Replaces BDE</li>
         <li>Commit control</li>
         <li>TSQLQuery always returns a read-only result set</li>
         <li>Implicit row based posting of updates via
         TSQLUpdate</li>
         <li>Minimizes use of SQL Server connections</li>
         <li>Retains most properties/methods of TQuery and
         TUpdateSQL</li>
         <li>No OCX:s or DLL:s (except for MS SQL Servers driver
         ntwdblib.dll and protocol drivers).</li>
         <li>Minimizes application footprint and startup times.</li>
         <li>Uses Delphis:s fields editor.</li>
         <li>High performance!</li>
         <li>Works with D3 Standard and Professional as well as
         Client Server version.</li>
      </ul>
      <h4>VCL-classes:</h4>
      <p>TSQLServer - connects the queries to a MS SQL Server.
      Methods for commit control.</p>
      <p>TSQLQuery - A query component that executes passthru
      SQL-statements. It can also cache all records in the record set
      and drop the server connection thus making it an ideal solution
      for applications with a large number of clients. The dataset is
      read-only and updates are performed thru the TSQLUpdate
      component.</p>
      <p>TSQLUpdate - Updates tables on the server. The updates are
      triggered on every post event on the corresponding TSQLQuery
      component.</p>
      <p>Some of our largest customers have used SQLQuery when
      building large scale web applications. We have done it here
      also in some customer projects. The reason our customers choose
      SQLQuery was that there are some memory leak problems with BDE,
      requiring them to restart the server at regular intervals. This
      problems hasn't been reported with SQLQuery.</p>
   </vendordescription>
   <ourcomments>
         <p>Although I generally prefer middleware-based solutions, in
      testing TSQLQuery has been very fast and easy to work with. It
      presents a very light deployment burden (a few DLLs), and the
      developers are very eager to fix any bugs as soon as they are
      reported. If your application will only need to work with MS
      SQL Server, 
      <b>try this product</b>!</p>
   </ourcomments>
   <internalnotes></internalnotes>
   <lastupdated></lastupdated>
   <lastupdatedby>Kyle Cordes</lastupdatedby>
   <active>1</active>
</product>
