toddasd (2/14/2013)

---

Well, we verified that the trigger fires only once with one row from each source. So the problem has nothing to do with the number of executions or the...

toddasd (2/14/2013)

---

So the trigger itself runs correctly from both sources. And there are no triggers on the tables BACK or BACK_RLFL. The only part left is the guts of the...

Both SSMS and SSIS reported 1 record which is the correct result.

What's next?

toddasd (2/14/2013)

---

Mark-545947 (2/14/2013)

---

No triggers anywhere else.

It has to be some setting issue in SSIS otherwise, why would work...

GilaMonster (2/14/2013)

---

How are you inserting from SSIS? If using one of the bulk load options, have you set 'fire triggers' property on?

p.s. Is hardcoding an OrderID in the trigger going...

No triggers anywhere else.

It has to be some setting issue in SSIS otherwise, why would it work from SSMS?

This is driving me crazy.

I understand your point of trigger firing on batches and not on rows. Then why doesn't my trigger work when I insert into it ONE record (FROM SSIS).

Here is my...

Sure it does for the situation of archiving what is not already there, but now you've introduced a new table, BACK_ARCHIVE. So I see four tables: BACK, RLFL, RLFL_BACK, and...

I don't understand.

I only have one row that I'm processing in SSIS. Just like I'd be processing one row with an INSERT statement from SSMS (which works flawlessly).

How do I...

Basically, use the mod(%) function to split your recs into three like so:

INSERT INTO TABLE_A

SELECT Tableid,sales

FROM (select ROW_NUMBER() OVER ( order by sales) as Tableid,name FROM myTable) tmp

WHERE TableId%3 =...

That does not work.

Here are my table layouts:

BACK Table:

OrderID ItemNo

--------- ---------

9813 ...

Thanks. That worked.

The exec sp.. worked like a charm!

I removed the quotes around the tables, so I guess bare invokation was OK after all.

Thanks a lot.:-)

No change. The same error.

I get the same error executing it in SSMS.