Tony303
asked on
sp_runwebtask: How does this sp get run
I have used the wizard to make a web page, I opted for the refresh on data change feature.
My web page however is only showing the data as at the time I used the web wizard. The data has changed.
I saved the wizard SQL statement and am happy that the field that changes will be an actual changing field. IE @whentype=10, @datachg=N'TABLE=DailyData COLUMN=ID'.
I have run sp_runwebtask manually in query analyser and then refreshed my web page and it works fine.
So how does the updating of data in the table fire off the sp_runwebtask??
Mine doesn't seem to.
My web page however is only showing the data as at the time I used the web wizard. The data has changed.
I saved the wizard SQL statement and am happy that the field that changes will be an actual changing field. IE @whentype=10, @datachg=N'TABLE=DailyData
I have run sp_runwebtask manually in query analyser and then refreshed my web page and it works fine.
So how does the updating of data in the table fire off the sp_runwebtask??
Mine doesn't seem to.
ASKER
Testing comments
ASKER
Ok, Cool.
I see 3 triggers one for insert, update and delete.
I will check those out.
No the table was not reuilt after the package was created.
Yes there is a column called ID.
Keep you posted.
Thanks
I see 3 triggers one for insert, update and delete.
I will check those out.
No the table was not reuilt after the package was created.
Yes there is a column called ID.
Keep you posted.
Thanks
So, as long as the triggers are testing for the change of column "id", the task should kick off...
ASKER
Ok, Here's where I am up to...
Here is the scenario, I ran SQL Profiler, opened query Analyser, deleted 1 line of Data.
Looked at profiler, saw my trigger had fired.
Opened my Web Page. Hey presto, data is as expected.
Next thought,
what about when my data is added, as I usually do via a SQL Job running a DTS package inserting data.
Started profiler, ran sql job, Ran OK. Looked at profiler results, no trigger fired. In my SQL job there is an insert and a delete statement, so I would expect the trigger to go off at least once.
Why wouldn't the trigger fire???
Here is the scenario, I ran SQL Profiler, opened query Analyser, deleted 1 line of Data.
Looked at profiler, saw my trigger had fired.
Opened my Web Page. Hey presto, data is as expected.
Next thought,
what about when my data is added, as I usually do via a SQL Job running a DTS package inserting data.
Started profiler, ran sql job, Ran OK. Looked at profiler results, no trigger fired. In my SQL job there is an insert and a delete statement, so I would expect the trigger to go off at least once.
Why wouldn't the trigger fire???
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
1
So, you might see if the triggers are on the table. If the table was rebuilt after the package was created, the triggers probably didn't get recreated....
Are you positive that DailyData has the column called ID?