execution plan for a SP with transaction differs from one without transaction

hi

i have this sql statement:
USE myDB
--begin tran t1
exec mySP 'parameters'
--rollback tran t1

(info: i want to rollback the transaction because i just want to test
the SP and see the execution plan)

the execution plan with the two transaction lines commented differs
completely from the execution plan if i uncomment the two lines

(info about the SP: it is creating a temporary table, doing a bulk
insert into it, and then doing an insert in a normal table from the
temporary table - simplified said)

i dont understand why the transactioning is affecting the execution
plan so extremly

thanks

regards
nedo

.

Relevant Pages

  • Re: Named Transactions
    ... You cannot do rollback using a transaction name to a BEGIN ... You have to do such rollback to a save point, created with SAVE TRAN. ... > My problem is not that 'rollback tran b' rolls the whole of transactions ...
    (microsoft.public.sqlserver.programming)
  • Re: Named Transactions
    ... rollback an "inner" transaction started with BEGIN TRAN. ... > transaction, but BOL says it must be the name of outermost 'Begin Tran'. ...
    (microsoft.public.sqlserver.programming)
  • Transaction question
    ... commit tran ... I thought that "internal" sql transaction will rollback automatically if the ... the first statement and tran didn't rolled back the first statement. ...
    (microsoft.public.sqlserver.programming)
  • Re: Named Transactions
    ... the 'Rollback Tran' has this synatx: ... transaction, but BOL says it must be the name of outermost 'Begin Tran'. ...
    (microsoft.public.sqlserver.programming)
  • Re: help - transaction control
    ... >transaction to successfully commit before any of the ... If a Rollback is issued anywhere along the ... > ROLLBACK TRAN ...
    (microsoft.public.sqlserver.programming)
Loading