Re: Help with an Update Statment
- From: "Tony Rogerson" <tonyrogerson@xxxxxxxxxx>
- Date: Wed, 28 May 2008 05:22:54 +0100
The next question is why do you want to build a table that has to be
constantly updated when you can use a VIEW that is always right?
This is fundemental design - beginners 101.
Summary tables are used to assist performance and scalability.
It could often take 20 seconds - 5 hours to work out the aggregations depending on the data set and the complexity of the calculations.
In OLTP data is read many many more times than it is written.
Now imagine your query method took 10 seconds to run for a single user; 100 users running the same query would flat line your CPU and probably push the query time out into minutes - not very scalable.
Unfortunetly because you are classroom based you don't see these real world problems; you are best getting out and doing a beginners programming job for a couple of years to get the necessary fundementals.
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
.
- Follow-Ups:
- Re: Help with an Update Statment
- From: Ed Murphy
- Re: Help with an Update Statment
- References:
- Re: Help with an Update Statment
- From: --CELKO--
- Re: Help with an Update Statment
- Prev by Date: Re: Strange connection problem
- Next by Date: Re: confusion over indexs via primary key and clustered index
- Previous by thread: Re: Help with an Update Statment
- Next by thread: Re: Help with an Update Statment
- Index(es):
Relevant Pages
|