It’s no problem, just a little to late to dig further onto the issue that’s all.

It’d be interesting to look at the apps, especially if you have source, but I know that may be out of the scope of … anything sane. But if you want insane, check out SQL Relay:

http://sqlrelay.sourceforge.net/index.html

It may be possible to catch them on legacy TDS protocol, and proxy them up to something newer.

I did notice the date after posting so I’m sorry about that, I’m currently following another post of yours about getting SQL 6.5 to work on Windows 10 as we have some legacy apps we need to keep working. I’ve tried upgrading the DB’s using all the methods available that i know, none allow the ancient application that hooks into it to function properly afterwards. But at a minimum all our security audits are finding the hosting OS to be the main point of failure, so having it working on windows 10 thorugh a hypervisor for the very few users that need it ocassionally will at least cover it from that perspective. Not ideal in production but needs must. Some interesting posts you have going on, keep up the good work is all i’ll say. 🙂

It very well could have been as well, but it’s been 8 years, and a few companies later..

I can’t recall if these were Dell or HP, other than that the old original servers certainly were Dell.

Mine may have been a combo of the NUMA domain, along with other constraints behind the scenes.

It always struck me as funny as this MSSQL server took extracts and transforms from Oracle to do custom reporting.

Band-aids are good fun, but if you don't address the actual problem, then you are just wasting everyones time.