Hi Moe –
Thanks for the insight. I understand that remote connections can be slow, but due to the internet connection speeds we have available to us that should not be an issue, this is not your average residential connection, we can transfer data at over 200MB, not Mbit, per second, out entire operation is cloud based.
Yes we do use a public cloud vendor, again not consumer class service, I could just stand SixBit on that box and RDC to it but that is not what I have been tasked to do.
What I think we have figured out is we are going to use private networking and make the SixBit MS MQL server, while in the cloud and running on a Kubernetes cluster , just appear on our internal network as a local MS MQL machine and instance as, SixBitMS1\sixbitdbs\OurSixBitDBName, it seems that the SixBit application doesn’t like to look at DNS names like db.ourfakesixbitserver.com or straight IP addresses 12.210.24.211 in the configuration panel. Can you confirm that ?
I do think if we can make this work without having to move to private networking, it would really make SixBit very portable, and you could have solid remote staff working remotely. Either way I am going to write up a tutorial / step by step on remote workers with sixbit.
I hope to hear from you Moe.
Best Regards
