a simple syntax error;

INSERTED is a virtual table that exists just inside the trigger...so there is no table called [TRAIN].[dbo].inserted [/b]

this should be:

SELECT @SRVSTAT = SRVSTAT,

...

Scripting this out is not all that difficult; I slapped together the examples just from the top of my head...you just have to do it one piece at a time....the...

if you can provide the actual CREATE TABLE statements for the tables in question, we could help you better;

sp_fkeys tblBOQ would give all the dependant tables to the table(is that...

yes, it will still work, you just have to follow all of the nodes of the tree:

for example, say my "Childtable" has FK records to it:

it might not be obvious,...

another way to do the same thing is to order by the length, then by the column:

select * from #temp order by len(Response),response

...well not the same thing, but similar...with the...

a much better solution is to use a set based operation; cursors are much slower.

you didn't provide any details, so here's a rough example:

by "copying", I'm assuming you mean to...

i would suggest adding a trace as well as the fine trigger example above; there's a thread here with my example of the trace i use:

http://www.sqlservercentral.com/Forums/FindPost745574.aspx

with the trace, you'd see...

with a table with no index, SQL server automatically creates a heap index, so there is at least some information on your table.

for the count, I'm guessing that although it's...

correct me i'm wrong, but you saved this script as a stored procedure, and the stored...

donato, are you trying to usee a CASE statement to return a desired value as a column, or as a WHERE condition?

SELECT

CASE

WHEN ITM.MNR_CD = '100' THEN '15'...

yes; like i had said before, I'd seen the issue in the past. I could never track down exactly what was the cause, but I found that changing that default...

Jeff Moden has a great quote on changing your mindset from row by row to "set based" thinking:

First step towards the paradigm shift of writing Set Based code:

Stop thinking...

i was kind of assuming the update was more complicated...you know 500-1000 might be a different multiplier, for example. there was no good reason for it, other than to allow...

here's my WAG based on your SQL:

UPDATE CP

SET CP.BaseRate = CASE

...

your cursor does not have an update statement...the only thing it is doing is fiddling with the variable @BaseRate i think.

did you forget to add the UPDATE to teh cursor?

WHILE...