Re: ANSI_WARNINGS error in Stored Procedure

From: john1811 (john1811.18f15g_at_mail.mcse.ms)
Date: 06/23/04

  • Next message: Mike: "Re: can not generate SSPI Context"
    Date: Wed, 23 Jun 2004 02:29:28 -0500
    
    

    Hi,
    I doesn't mater which Database you use. Even in SQL server when we
    link two different server, we get this problem. Once way of solving
    this is create the stored procedure in SQL server in the format below

    SET ANSI_NULLS OFF
    SET ANSI_WARNINGS OFF
    GO

    CREATE PROCEDURE dbo.MBUTotal
    AS

    BODY of THE STORED PROCEDURE
    RETURN
    GO

    SET ANSI_NULLS OFF
    SET ANSI_WARNINGS OFF

    This will solve this problem. Atleast for me it helped to solve the
    problem.

    Regards,
    John Solomon. J

    Noe Carranza wrote:
    > *Hi Russell, thanks a lot for replying...
    >
    > you are correct, the linked server is a JDEdwards.
    >
    > I was trying to create the stored procedure from the New Stored
    > Procedure Window, instead of the Query Analyzer. I dont know why I
    > didnt
    > try the Query Analyzer before.
    >
    > So there's a tip for all of you people, use the query analyzer and
    > forget about problems. Thanks again Russell! :)
    >
    > Noe.
    >
    > *** Sent via Developersdex http://www.examnotes.net ***
    > Don't just participate in USENET...get rewarded for it! *

    --
    john1811
    ------------------------------------------------------------------------
    Posted via http://www.mcse.ms
    ------------------------------------------------------------------------
    View this thread: http://www.mcse.ms/message291544.html
     
    

  • Next message: Mike: "Re: can not generate SSPI Context"

    Relevant Pages

    • Re: How to get list of EventClasses in MSSQLServer2000
      ... statement inside a stored procedure has completed.') ... SQL Server statement or stored procedure.') ... Plan','Displays the plan tree of the Transact-SQL statement executed.') ... Login','Occurs when a SQL Server login is added or removed; ...
      (microsoft.public.sqlserver.security)
    • 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)
    • Re: Accessing FoxPro Free Table
      ... which the SQL Server service is running. ... account, ... > If you are creating a stored procedure and you want> to make sure that the procedure definition cannot be> viewed by other users, you can use the WITH ENCRYPTION> clause. ... The procedure definition is then stored in an> unreadable form. ...
      (microsoft.public.data.odbc)
    • Stored procedure does not complete until result set is retrieved from ODBC
      ... I have a SQL Server Stored procedure that I am executing via ODBC. ... -- Start Code without cursor ...
      (microsoft.public.sqlserver.odbc)