Re: Speeding up multiple updates
- From: "brian" <brian.lukoff@xxxxxxxxx>
- Date: 10 Oct 2006 12:24:43 -0700
Bob Barrows [MVP] wrote:
Absolutely not. It's not the worst thing you could do, but it's close.
Almost worse than creating multiple columns to hold the individual data
values.
My solution involves a single UPDATE statement as well. And data
integrity is not compromised.
Why is this so bad? There is no validation done on the values (the
user enters the data), so I don't think data integrity would be a
problem. (Unless I'm not understanding what you mean.) Also, having
one column with delimited values seems simpler and would seem to take
less time on the database end since the ASP code would put together
(and take apart) the delimited list of values. It's not an elegant
solution, but it seems like it should work and alleviate the problems I
have been experiencing with timeouts, locking, and cascading blocking.
Brian
.
- Follow-Ups:
- Re: Speeding up multiple updates
- From: Mike Brind
- Re: Speeding up multiple updates
- From: Bob Barrows [MVP]
- Re: Speeding up multiple updates
- References:
- Speeding up multiple updates
- From: brian . lukoff
- Re: Speeding up multiple updates
- From: Bob Barrows [MVP]
- Re: Speeding up multiple updates
- From: brian
- Re: Speeding up multiple updates
- From: Bob Barrows [MVP]
- Speeding up multiple updates
- Prev by Date: Re: Code inside database
- Next by Date: Re: Speeding up multiple updates
- Previous by thread: Re: Speeding up multiple updates
- Next by thread: Re: Speeding up multiple updates
- Index(es):
Relevant Pages
|