|
Hi there At the moment the DB server sits on our own Windows 2019 box. I have been asked to look at the procedure for moving that and web servers/services to Azure. There was a question about connections for one running on that platform on this forum, but as yet cannot find a white paper, or even definitive confirmation that this is possible. All searches seem to pull up MS SQL (spit) and as such are not very helpful. Does anyone have an information and/or pitfalls with this? Thanks |
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 02 Sep '21, 16:05
question was seen: 1,708 times
last updated: 03 Sep '21, 12:35
FWIW here's a general FAQ on running SQL Anywhere in the cloud, not restricted to Azure...
Yup, that is what I was referring to with 'There was a question about connections for one running on that platform on this forum'
I would not expect that there is anything special about connecting to a SQL Anywhere database on a hosted server like Azure than running on a on-premise server. The server would needed to configured such that the host and port is visible to the world and then you would simply use Firewall Connections documentation to configure the client. See https://help.sap.com/viewer/61ecb3d4d8be4baaa07cc4db0ddb5d0a/17.0/en-US/3bcaf8366c5f101483eafcd85cddb0e5.html?q=firewall.
Here is a reference to how to open ports on Azure. https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nsg-quickstart-portal.
I have not specifically tried this on Azure but have used the Firewall Connections several times to assist customers who had problems connecting to database servers behind the firewall.
Basically the DB server should only be visible to a Web Service/Server and admin, as it is at the moment. Web servers and web services are the front end and should be the only IP that connects. At first glance it looks like comparable hardware rental runs out at the cost of building an on-premises server over two months, the on-premises one good for five or six years. I really am struggling to figure out any advantage to moving it.