May 14, 2008 at 9:47 pm
INSERT INTO [Vimas].[dbo].[TempBatch]
Select TransID From Batchheader (nolock)
where DateCreated < GetDate() -180
May 14, 2008 at 10:22 pm
What error are you getting?
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
May 14, 2008 at 10:31 pm
It first stated '0 rows affected', THEN it worked.
What would cause that?
May 15, 2008 at 5:33 am
Is this part of a bigger batch?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 15, 2008 at 5:44 am
Yes, it's part of a bigger batch process. An SSIS package that creates a temp table to insert a key TransID from a header table into a temp table then moves onto other steps in the SSIS package process.
May 15, 2008 at 5:52 am
I guess I meant, is this statement just one of a batch of TSQL statements? You may have received the 0 rows affected from another part of the query.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply