Results 1 to 4 of 4

Thread: Silencing iSQL

  1. #1
    Join Date
    Jan 2003
    Posts
    2

    Unanswered: Silencing iSQL

    Hi All

    Apologies in advance is this is a stupid newbie question answered in some FAQ that has so far eluded me. I have done searches but to no avail.

    I'm using an update cursor within a stored procedure to assign each row of a table a serial and random number. While running the procedure, iSQL is spitting out the values for each row as it is updated. I'm sure this is impacting on the procedure's performance. How do I tell iSQL to shut up until the procedure is finished?

    TIA

    Simon

  2. #2
    Join Date
    Jan 2003
    Posts
    28

    Re: Silencing iSQL

    Is it the number of rows updated that is getting spit out or perhaps is it a select statement without variable assignment taht may be spitting these messages out?

  3. #3
    Join Date
    Jan 2003
    Posts
    2

    Re: Silencing iSQL

    Originally posted by robgee
    Is it the number of rows updated that is getting spit out or perhaps is it a select statement without variable assignment taht may be spitting these messages out?
    Thanks robgee, you're spot on. I wasn't interested in the values of the fields before the update so was just doing a 'fetch cursor_name'. I'm now assigning the values to some internal variables and it's all gone quiet.

    Thanks again

    Simon

  4. #4
    Join Date
    Jan 2003
    Posts
    28

    Re: Silencing iSQL

    Glad to be of help.

    Rob

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •