I wonder why there's always the justification that developers are expensive when it is they that wrote the code that's causing the problem. Having them write the same crap code faster is a totally losing battle.
If you want to do something right, train the developers to write better code, and then make their jobs (and their managers' jobs) depend on it.
As soon as you've accomplished such a thing, you'll find that the cost of developers will actually drop a lot compared to their throughput which no longer requires either functional or performance rework.
Like the old saying goes... "What if we train our developers and they leave"? Better question... "What happens if we don't and they stay?"
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair
When you put the right degree of spin on it, the number 318
is also a glyph that describes the nature of a DBAs job. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs