Home All Groups Group Topic Archive Search About

The command(s) completed successfully. - Can i turn this output off?

Author
9 Dec 2005 1:51 PM
Immy
Hi all,

can i turn off the "The command(s) completed successfully." message that is
returned after a proc is executed that returns no data?

Thanks
mmy

Author
9 Dec 2005 2:08 PM
Aaron Bertrand [SQL Server MVP]
I don't think so.  What is the problem with this message?  Why do you care?
If you have no row(s) affected, how else do you want to be notified that the
procedure has finished executing?



Show quote
"Immy" <imtiaz_ul***@hotmail.com> wrote in message
news:ubJqCfM$FHA.2608@TK2MSFTNGP11.phx.gbl...
> Hi all,
>
> can i turn off the "The command(s) completed successfully." message that
> is returned after a proc is executed that returns no data?
>
> Thanks
> mmy
>
Author
9 Dec 2005 2:56 PM
Immy
Well.... the problem is down to the Microsoft reporting service!!!
If this is returned in the output of a proc execution, then the report that
was running at that time will "crash and burn".
Thats why i need to turn it off. There are other methods i can employ, but
this would be the easiest method.


Show quote
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:eqqRvmM$FHA.2156@TK2MSFTNGP11.phx.gbl...
>I don't think so.  What is the problem with this message?  Why do you care?
>If you have no row(s) affected, how else do you want to be notified that
>the procedure has finished executing?
>
>
>
> "Immy" <imtiaz_ul***@hotmail.com> wrote in message
> news:ubJqCfM$FHA.2608@TK2MSFTNGP11.phx.gbl...
>> Hi all,
>>
>> can i turn off the "The command(s) completed successfully." message that
>> is returned after a proc is executed that returns no data?
>>
>> Thanks
>> mmy
>>
>
>
Author
9 Dec 2005 3:05 PM
JT
What are you executing inside the stored procedure that would return this
message?

Show quote
>>> can i turn off the "The command(s) completed successfully." message that
>>> is returned after a proc is executed that returns no data?
>>>
>>> Thanks
>>> mmy
>>>
>>
>>
>
>
Author
9 Dec 2005 3:16 PM
Aaron Bertrand [SQL Server MVP]
> Well.... the problem is down to the Microsoft reporting service!!!
> If this is returned in the output of a proc execution, then the report
> that was running at that time will "crash and burn".

Why do you think it is because of the command completion message?  Do you
have any evidence to support this?  Does your procedure say SET NOCOUNT ON
at the top?
Author
9 Dec 2005 3:39 PM
Immy
YES !!!! I use set nocounts etc... and yes, I have evidence because if i
return anything else in the result set it works.
The reason reporting service falls over is because it is expecting columns
to come back in a particular format, thus, when the message "the command
completed) is returned, it isn't doesnt fit the column expected.




Show quote
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:uOJfJNN$FHA.2740@tk2msftngp13.phx.gbl...
>> Well.... the problem is down to the Microsoft reporting service!!!
>> If this is returned in the output of a proc execution, then the report
>> that was running at that time will "crash and burn".
>
> Why do you think it is because of the command completion message?  Do you
> have any evidence to support this?  Does your procedure say SET NOCOUNT ON
> at the top?
>
Author
9 Dec 2005 3:47 PM
Aaron Bertrand [SQL Server MVP]
> YES !!!! I use set nocounts etc... and yes, I have evidence because if i
> return anything else in the result set it works.
> The reason reporting service falls over is because it is expecting columns
> to come back in a particular format, thus, when the message "the command
> completed) is returned, it isn't doesnt fit the column expected.

UHHHH, THAT ISN'T A COLUMN!   If your reporting service "falls over because
it is expecting columns" then why don't you try RETURNING COLUMNS!!!???
Author
9 Dec 2005 4:05 PM
Immy
I understand the workarounds i have and I also know that IT ISNT A COLUMN!!!
I wasn't looking for comments from people that were pointing out the
obvious, simlpy asking if.... IN GENERAL, there is a way to turn of the
message. Clearly I've stumbled across people that try to belittle others
rather than offer suggestions.

Thanks


Show quote
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:OWLoXeN$FHA.2036@TK2MSFTNGP14.phx.gbl...
>> YES !!!! I use set nocounts etc... and yes, I have evidence because if i
>> return anything else in the result set it works.
>> The reason reporting service falls over is because it is expecting
>> columns to come back in a particular format, thus, when the message "the
>> command completed) is returned, it isn't doesnt fit the column expected.
>
> UHHHH, THAT ISN'T A COLUMN!   If your reporting service "falls over
> because it is expecting columns" then why don't you try RETURNING
> COLUMNS!!!???
>
>
>
Author
9 Dec 2005 4:16 PM
JT
What are you executing inside the stored procedure that would return the
message? Some type of DBCC command? Normally this doesn't get returned.

Show quote
"Immy" <imtiaz_ul***@hotmail.com> wrote in message
news:%23iRsupN$FHA.3308@TK2MSFTNGP11.phx.gbl...
>I understand the workarounds i have and I also know that IT ISNT A
>COLUMN!!! I wasn't looking for comments from people that were pointing out
>the obvious, simlpy asking if.... IN GENERAL, there is a way to turn of the
>message. Clearly I've stumbled across people that try to belittle others
>rather than offer suggestions.
>
> Thanks
>
>
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in
> message news:OWLoXeN$FHA.2036@TK2MSFTNGP14.phx.gbl...
>>> YES !!!! I use set nocounts etc... and yes, I have evidence because if i
>>> return anything else in the result set it works.
>>> The reason reporting service falls over is because it is expecting
>>> columns to come back in a particular format, thus, when the message "the
>>> command completed) is returned, it isn't doesnt fit the column expected.
>>
>> UHHHH, THAT ISN'T A COLUMN!   If your reporting service "falls over
>> because it is expecting columns" then why don't you try RETURNING
>> COLUMNS!!!???
>>
>>
>>
>
>
Author
9 Dec 2005 4:19 PM
Aaron Bertrand [SQL Server MVP]
>I understand the workarounds i have and I also know that IT ISNT A
>COLUMN!!!

Is that why you said "it isn't doesnt fit the column expected"?

> I wasn't looking for comments from people that were pointing out the
> obvious, simlpy asking if.... IN GENERAL, there is a way to turn of the
> message.

It's not going to fix the problem.  Your reporting services, apparently, are
still expecting columns.  They are not currently getting a column at all,
regardless of whether the informational message is there.  Once again,
regardless of what evidence you think you have, this problem is NOT caused
by the command completed successfully message.

> Clearly I've stumbled across people that try to belittle others rather
> than offer suggestions.

Belittle?  First day here?  Ever met Celko?

See ya, have fun trying to remove that "column"...
Author
9 Dec 2005 8:01 PM
Tibor Karaszi
That message is not created by SQL Server, it is created by Query Analyzer. So, there's nothing to
turn off. The problem is most probably because RS expects a table and doesn't get a table. I'm no RS
expert, but perhaps you can post to the RS group and see if they can confirm and suggest actions...

Show quote
"Immy" <imtiaz_ul***@hotmail.com> wrote in message news:%23iRsupN$FHA.3308@TK2MSFTNGP11.phx.gbl...
>I understand the workarounds i have and I also know that IT ISNT A COLUMN!!! I wasn't looking for
>comments from people that were pointing out the obvious, simlpy asking if.... IN GENERAL, there is
>a way to turn of the message. Clearly I've stumbled across people that try to belittle others
>rather than offer suggestions.
>
> Thanks
>
>
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
> news:OWLoXeN$FHA.2036@TK2MSFTNGP14.phx.gbl...
>>> YES !!!! I use set nocounts etc... and yes, I have evidence because if i return anything else in
>>> the result set it works.
>>> The reason reporting service falls over is because it is expecting columns to come back in a
>>> particular format, thus, when the message "the command completed) is returned, it isn't doesnt
>>> fit the column expected.
>>
>> UHHHH, THAT ISN'T A COLUMN!   If your reporting service "falls over because it is expecting
>> columns" then why don't you try RETURNING COLUMNS!!!???
>>
>>
>>
>
>
Author
9 Dec 2005 4:27 PM
Trey Walpole
I would seriously doubt that this message is the problem, as this
message doesn't get returned to the calling process. If it were, you
would get crash and burn all the time, as this message is there all the
time.

What happens inside the stored procedure itself if there is no data?
Please post the code, so we can check to see what's going on.
Without seeing the code, my first assumption would be that it isn't
returning a result set to the caller. If it were returning a result set
- even an empty one - it would still have the expected schema.

Immy wrote:
Show quote
> Well.... the problem is down to the Microsoft reporting service!!!
> If this is returned in the output of a proc execution, then the report that
> was running at that time will "crash and burn".
> Thats why i need to turn it off. There are other methods i can employ, but
> this would be the easiest method.
>
>
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
> news:eqqRvmM$FHA.2156@TK2MSFTNGP11.phx.gbl...
>
>>I don't think so.  What is the problem with this message?  Why do you care?
>>If you have no row(s) affected, how else do you want to be notified that
>>the procedure has finished executing?
>>
>>
>>
>>"Immy" <imtiaz_ul***@hotmail.com> wrote in message
>>news:ubJqCfM$FHA.2608@TK2MSFTNGP11.phx.gbl...
>>
>>>Hi all,
>>>
>>>can i turn off the "The command(s) completed successfully." message that
>>>is returned after a proc is executed that returns no data?
>>>
>>>Thanks
>>>mmy
>>>
>>
>>
>
>

AddThis Social Bookmark Button