you should be creating a trigger on table1 for that. I didnt understand what you meant by I don't want table1 to carry the additional process of dumping it's data to table2. In any case, trigger gets fired on event happening on table1 and it takes care of dumping process and will be fetching data from internal temporary table INSERTED which will have same structure as table1
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/
What I really want to do is this, since in all the data entry is happening in table1 and so the there is a process that is going on. If the trigger will also be done on table1 there will be another process that will happen.
But anyway I think i will just use a Job scheduler to run the stored proc.
What I really want to do is this, since in all the data entry is happening in table1 and so the there is a process that is going on. If the trigger will also be done on table1 there will be another process that will happen.
But anyway I think i will just use a Job scheduler to run the stored proc.
Thank you very much in your response.
still didnt understand why its a concern for you Anyways you can go with scheduler approach though it wont take place at real time.
------------------------------------------------------------------------------------------------------ SQL Server MVP http://visakhm.blogspot.com/
SQL Event Trigger
Posted - 03/07/2012 : 19:06:47
