4 ms·
Rather than write another reply, I'll link you to my thoughts: https://news.ycombinator.com/item?id=9928688 https://news.ycombinator.com/item?id=9928688
by batou 11y ago
Rather than write another reply, I'll link you to my thoughts: https://news.ycombinator.com/item?id=9928688 https://news.ycombinator.com/item?id=9928688
- redcalx 11y agoNice reference discussion, thanks. Sounds like we're on the same wavelength. Our main issue (IMO) is that if you get a SQL Server person in to solve SQL Server performance issues then you're likely going to go down the route of one massive all powerful SQL Server box which just compounds the problem. A broader solution of moving away from pure SQLServer and towards distributed work, caching layers, etc. is probably a saner long term path to take. But in business short term thinking generally takes precedence over long term.
- batou 11y agoThat's very true which is why we wrangled the architecture off the database folk :)