We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

sp_runwebtask: How does this sp get run

Tony303
Tony303 asked
on
Medium Priority
621 Views
Last Modified: 2007-12-19
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.




Comment
Watch Question

Top Expert 2004

Commented:
When you create a webtask, triggers are added to the table you specified when you create the task.

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?
CERTIFIED EXPERT

Author

Commented:
Testing comments
CERTIFIED EXPERT

Author

Commented:
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
Top Expert 2004

Commented:
So, as long as the triggers are testing for the change of column "id", the task should kick off...
CERTIFIED EXPERT

Author

Commented:
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???

Top Expert 2004
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
CERTIFIED EXPERT

Author

Commented:
1
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.