you can attack my code building skills if you want but the fact remains that if you have a high physical disk queue on a drive thats only used for the dB file then you will benefit tremendously from upgrading to SSDs. in my scenario my CPU remained at 2-5% while my physical disk Queue droped almost to 0.
today they may not have the reliability you have come to expect from traditional HDs but they will replace traditional HDs completely probably within 10 years.
I wasn't attacking anyone's code building skills in particular, let alone yours. I was simply stating that people tend to get even lazier when such miracles as SSD come into play and that people have to remember there are other problems other than hefty disk queues. Hefty disk queues are normally accompanied by hefty CPU loads and you need to consider the CPUs, as well.
BWAAA-HAAAA!!!! I just thought of something. Wouldn't it be ironic if the SSDs had such a high failure rate because of the fat disk queues caused by crap code that people were trying to solve?
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.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs