Re: MSSQL vs. SYBASE

From: Lewis Howell (lou_junkmail_at_yahoo.com)
Date: 08/04/04 

Date: Wed, 4 Aug 2004 02:37:22 -0400

Adding RAISERROR is not an option, we would have to edit 1,000+ stored
procs ().

"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns9536E34A75A35Yazorman@127.0.0.1...
> Lewis Howell (lou_junkmail@yahoo.com) writes:
> > I am converting to MSSQL SERVER from SYBASE. In our client side
> > application we use callback procedures with CT_LIB to get information
> > back from the server during a lengthy process or an infinite (looping)
> > process controlled by or called within a stored procedure. I can not
> > find any type of callback for MSSQL.
> >
> > Example, I would normally have a SELECT statement within my loop or
> > beginning of an infinite stored procedure or any stored procedure which
> > would make the stored proc have multiple result sets. The contents of
> > the SELECT would be my feedback that would be processed by the callback
> > procedure in SYBASE. With MSSQL, only if I cancel the stored proc then
> > all the SELECTs come back at one time in the end...they do not get
> > returned at any ohter point.
> >
> > I am using ADO with the {SQL SERVER} driver to SQL SERVER 2000 with SP3.
> > MDAC 2.7 or 2.8. Coding in DELPHI 6.
>
> That is correct, there are no callbacks on results in any of the Microsoft
> APIs. In ADO .Net you can get callbacks on messages, as you can in DB-
> Library of course.
>
> I have not explored this area myself, but since tools like Query Analyzer
> can present data on the fly, I would assume that this is possible. ADO
> is however a high-level library which does much behind your back to be
> reliable in this area. I played a little with it, and found that I could
> get the results sets as they came if I:
> o added a RAISERROR WITH NOWAIT after the SELECT statement
> o used a server-side cursor.
>
> ADO does also have asynchronous alternatives, and they may work better,
> but I have not explored these myself.
>
> In the end, you may prefer to use the ODBC interface, which is more
> low-level, but does not remove subtle functionality which ADO does.
> Yet an alterantive is the OLE DB interface which definitely looks
> dauting at first, but once you get through the good samples, you are
> on track for the simple stuff. But I don't know if you can do that in
> Delphi.
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

Relevant Pages

  • Re: SQL Server extremely slow
    ... terms of what is meant by a dis-connected ado recordset. ... table in a mdb file could be considered disconnected from the server ... Well, ok, but keep in mind the disk drive is on sql server! ... 10 reocrds from the server via odbc does not produce more ...
    (comp.databases.ms-access)
  • Re: Variable in SQL Where Statement in =?windows-1252?Q?=93Pass_?= =?windows-1252?Q?__Throug
    ... to a server, either. ... Well, when using ADO, we can indeed bind the resultset of stored procedure to a form and still have it updatable, providing we follow same set of rules we have to follow for writing queries for a form's recordsource. ... It's only in the case where you've bound a form to ADO recordset would you get a ADO recordset from the form's recordset. ... I actually never though to overlay a parameter query on top of a passthrough query, but that's two objects for one function, and I'm loath to create several objects. ...
    (microsoft.public.access.modulesdaovba)
  • Re: CHANGING from DAO to RDO
    ... To boost the speed we use Terminal Server 2003 and it definetly helps on the fact that we get less corruption, but certain queries take awhile and we want to add more users. ... I don't know _where_ you got the idea that ADO and RDO were the only methods to access SQL Server. ... In fact, I have never heard of anyone using RDO with an Access database, only, in the past, with the separate VB product. ... The VB crowd abandoned it for ADO with SQL Server, even though they, too, could use DAO and, for them too, DAO was simpler and easier. ...
    (microsoft.public.access.modulesdaovba)
  • /dev2/root still mounted after boot
    ... I've been running a Debian Woody server for web and mail for a couple years, ... proc /proc proc rw 0 0 ... devpts /dev/pts devpts rw 0 0 ... Output from quotacheck... ...
    (Debian-User)
  • RE: Moving data back and forth between Excel and SQL Server
    ... your database you should look into using ADO. ... ADO proides an object model to let you work with data via SQL/ODBC. ... records, or to update/add records, or even to create or modify tables - all ... MyRs.Update ' updates recordset on server ...
    (microsoft.public.excel.programming)