TheSQLGuru - Tuesday, February 6, 2018 3:56 PM
Hopefully my original post didn't sound like I was bagging on Pure Storage... That wasn't my intention. Moving from spinning rust to Pure was like moving from grand dad's old Ford to a Koenigsegg...
As far as what got communicated to who... It was roughly 3 years ago and my personal, hands on, involvement was pretty limited. I have no idea who our contact at Pure was at that time.
I just remember working through the test plans with the two DBA's who worked on the project, helping to do some follow-up validation and general discussions about what needed to be done with index maintenance procedures in terms of keeping or dropping the existing SQL Server PAGE/ROW compression setting.
Of course that was 3 years ago, so I have no idea if Pure has updates their proprietary compression algorithm since then. It may be worth a retest...
Neither of the two aforementioned DBA's are still with the company but I may try to contact them and see if either held on to their original test procedures.
Keven - Let me know if you have specific tests you'd like to see run... I'm always interested in your insights and I'd be happy to work with you if you're interested.