Re: "On Error Resume Next" in SQL Server

From: Louis Davidson (dr_dontspamme_sql_at_hotmail.com)
Date: 02/04/05 

Date: Fri, 4 Feb 2005 10:40:41 -0600

When you are running your query in query analyzer, does it stop running? If
so, then please post the code. If it doesn't, then it is your code that is
causing it to stop. Just have your calling code ignore the errors and
continue on. 

-- 
----------------------------------------------------------------------------
Louis Davidson - drsql@hotmail.com
SQL Server MVP
Compass Technology Management - www.compass.net
Pro SQL Server 2000 Database Design - 
http://www.apress.com/book/bookDisplay.html?bID=266
Blog - http://spaces.msn.com/members/drsql/
Note: Please reply to the newsgroups only unless you are interested in 
consulting services.  All other replies may be ignored :)
"Andy Wakeling" <anonymous@discussions.microsoft.com> wrote in message 
news:203501c50ad3$6ee202d0$a601280a@phx.gbl...
>I am executing a stored procedure that uses a cursor to do
> a CONTAINS search for each record and to produce a result
> set from that for output. The trouble is that if a good
> old "ignored words" error occurs for one of the records
> the procedure stops running. I need this to carry on
> running regardless of this as the only reason an error
> would occur would be due to bad user input which does not
> bother me and can therefore be "ignored".
>
> I have followed the advice in the KB article at
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;246800 for formatting input for CONTAINS searches but
> there is always some nasty ASCII/UNICODE character that
> slips through.
>
> Is there a method to isolate the full-text search (or any
> part of the procedure for that matter) and to guarantee
> that my stored procedure will run to the end of the cursor?
>
> Any help would be much appreciated.

Relevant Pages

  • Re: Is sql server as good as access 97?
    ... Once you really get into using Query Analyzer for writing your ... Transact-SQL and for formulating 'queries' for exporting to your code, ... resulting stored procedure runs in a small fraction of the time it took to ... Unfortunately the database I am converting ...
    (microsoft.public.sqlserver.programming)
  • RE: Differences in execution times for a stored procedure
    ... If OleDb, ... "Vincent Keller" wrote:> I am trying to execute a time-consuming stored procedure in my application. ... > Are there some known performance differences in executing a query directly through Query Analyzer and through ADO.NET? ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Exception: The SqlTransaction has completed; it is no longer usabl
    ... > I hv encountered this exception 'The SqlTransaction has completed; ... returning around 9000 rows in a DataSet and back to the app. ... > When that exception is thrown, I tried running the same stored procedure ... > I was thinking if Query Analyzer can return data very quickly... ...
    (microsoft.public.dotnet.framework.adonet)
  • ADO vs Query Analyzer Performance -- Its not parameter sniffing
    ... Immediately calling the same stored procedure WITH SAME PARAMETERS from ... Query Analyzer returns the results almost immediately. ... Analyzer call returned very quickly (40 seconds from app, ... ADO/SQLOLEDB interaction with SQL Server is different than Query Analyzer. ...
    (microsoft.public.data.ado)
  • SQLOLEDB vs Query Analyzer performance (not parameter sniffing)
    ... Immediately calling the same stored procedure WITH SAME PARAMETERS from ... Query Analyzer returns the results almost immediately. ... Analyzer call returned very quickly (40 seconds from app, ... ADO/SQLOLEDB interaction with SQL Server is different than Query Analyzer. ...
    (microsoft.public.data.oledb)
Quantcast