View + INSTEAD OF UPDATE + UPDATE FROM
From: Hugo Kornelis (hugo_at_pe_NO_rFact.in_SPAM_fo)
Date: 09/28/04
- Next message: Ian: "Re: Maths Formula Question"
- Previous message: Per Hultqvist: "Re: Syntax questions"
- Next in thread: Al Tenhundfeld: "Re: View + INSTEAD OF UPDATE + UPDATE FROM"
- Reply: Al Tenhundfeld: "Re: View + INSTEAD OF UPDATE + UPDATE FROM"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 28 Sep 2004 11:40:30 +0200
I guess I should have read the small print in Books Online first.....
After noticing the huge performance difference between ANSI standard
UPDATE syntax and proprietary UPDATE FROM syntax, I decided to use the
latter for a time critical system.
After writing 323 procedures, totaling 7169 lines of code, I go to the
test server, import all my code and start a test.
Server: Msg 4422, Level 16, State 1, Procedure XXXXX, Line 7
View 'dbo.YYYYY' has an INSTEAD OF UPDATE trigger and cannot be a target
of an UPDATE FROM statement.
Drat! Time to revisit 7169 lines of code, I'm afraid......
Unless somebody here knows of an easy workaround?
Oh - I'd also be interested to know WHY the UPDATE FROM syntax can't be
used for views with an instead of update trigger. If I read BOL correctly,
it can be used on a view with an AFTER trigger, it can be used on a table
with an INSTEAD OF trigger - just not on a view with in instead of
trigger. Many of SQL Server's limitations make sense when you consider it
from an architectural point of view. I fail to see the sense for this
limitation. Anyone care to enlighten me?
TIA!
Best, Hugo
-- (Remove _NO_ and _SPAM_ to get my e-mail address)
- Next message: Ian: "Re: Maths Formula Question"
- Previous message: Per Hultqvist: "Re: Syntax questions"
- Next in thread: Al Tenhundfeld: "Re: View + INSTEAD OF UPDATE + UPDATE FROM"
- Reply: Al Tenhundfeld: "Re: View + INSTEAD OF UPDATE + UPDATE FROM"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|