Re: Problem with execution
From: John Bell (jbellnewsposts_at_hotmail.com)
Date: 10/25/04
- Next message: TLCom: "INSTEAD OF UPDATE Trigger"
- Previous message: Prabhat: "Re: Stored Procedure to Connect a DBF File"
- In reply to: Johny: "Problem with execution"
- Next in thread: Johny: "Re: Problem with execution"
- Reply: Johny: "Re: Problem with execution"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 25 Oct 2004 13:03:11 +0100
Hi
You don't say if it just hangs (in which case you are probably blocked) or
if you get an error message. You may want to use TRUNCATE instead of delete
if you wish to delete everything from the table.
It may also be an idea to put this in a transaction and add error handling
(see @@ERROR in Books online).
John
"Johny" <goky2002@beograd.com> wrote in message
news:uGbIJPouEHA.1420@TK2MSFTNGP10.phx.gbl...
> have Stored procedure spAdmin_Do And I try to execute it from application
(I
> can execute it from Query Analyzer).
> The procedure simply stop at the first EXEC 'delete Do.dbo.Admin_Do' and
> don't continue.
> If I delete that line procedure again stop at the first EXEC.
>
> Is it problem if I have more EXEC in procedure or How can I solve this on
> some different way?
>
> The procedure spAdmin_Do:
>
>
> CREATE PROCEDURE spAdmin_Do
> (
> @sFiscalYear varchar(10)
> )
> AS
> @sQueryPart1 varchar(1000),
> @sQueryPart2 varchar(1000),
> @sQueryPart3 varchar(1000)
>
> SET @sQueryPart1 = " Some query "
> SET @sQueryPart2 = " Some query "
> SET @sQueryPart3 = " Some query "
>
> SET DATEFORMAT dmy
> Exec ('delete Do.dbo.Admin_Do')
> EXEC(@sQueryPart1)
>
> EXEC(@sQueryPart2)
> EXEC(@sQueryPart3)
> GO
>
>
>
- Next message: TLCom: "INSTEAD OF UPDATE Trigger"
- Previous message: Prabhat: "Re: Stored Procedure to Connect a DBF File"
- In reply to: Johny: "Problem with execution"
- Next in thread: Johny: "Re: Problem with execution"
- Reply: Johny: "Re: Problem with execution"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|