3 ms·

This was in the early days of HANA, I'm sure they've fixed the defects by now, but it was shocking to pay nose-bleed prices for every 64gb shard, and then have

by panarky 10mo ago

This was in the early days of HANA, I'm sure they've fixed the defects by now, but it was shocking to pay nose-bleed prices for every 64gb shard, and then have basic SQL return provably incorrect results. It was a catastrophe, and after spending heavily on consultants to work around the defects, the organization eventually switched to SQL Server.

jiggawatts 10mo ago
> return provably incorrect results. Again, you're burying the lede here. It's like the Linux fanboi stating without evidence that Windows will just accept any user name without a password, and then refusing to elaborate on that claim. Like... wat? SAP HANA may have its faults, but I've never heard of pervasive data corruption as one of them.
- spwa4 10mo ago
  > It's like the Linux fanboi stating without evidence that Windows will just accept any user name without a password, and then refusing to elaborate on that claim. Like... wat? Did you enter the correct NSAKEY username?