I love to see a creative solution to a technical problem.
How can I get that user out of my table quickly by JackLi
Great creative solution using indexed persisted computed columns.
The beauty of indexed persisted computed columns is that, yes, you have to pay the cost of doing the computation, but you only pay that cost at the point where you INSERT or UPDATE that particular column. If the data is mostly static as it is in this case, the one-time cost is very small.
Rob Garrison's writings on Data Architecture: Hadoop, SQL Server, performance, design, testing, best-practices, and automation.
Monday, January 28, 2013
Wednesday, January 16, 2013
You Can’t Sacrifice Partition Tolerance
Just finished reading this excellent article by Coda Hale:
I thought the bit about yield versus uptime was very interesting, as was the bit about harvest (harvest = data available/complete data). Historically, [the corporate] we have built systems that sacrifice yield in the event of a failure. I like the challenge/opportunity of building a system that reduces harvest but maintains yield.
Subscribe to:
Posts (Atom)