April 4, 2024 at 2:11 pm
My opinion - don't. As far as I am aware, there are no official apps from Microsoft for connecting to SQL Server for iPad. ANY 3rd party app runs the risk of pulling in data without your consent or knowledge. Who knows where that data is going, and worst case lets say they capture your credentials. Can you afford to have some random people on the internet connecting to your SQL instance?
But, if you REALLY want to do that, then the fields are clearly marked. You have the host name, the port, the instance name, the database name, the username and password. Which part is confusing? The alias is likely what that app is going to call the connection.
I do see in your screenshot you are NOT connected to wifi though... is your SQL instance really exposed to the internet? If so, I'd fix that pretty darn quick. If your SQL instance is exposed to the internet, someone is going to target it and best case, you get hit with a DOS attack (or DDOS); worst case they gain access to the sysadmin level access to the DB and you really don't want that.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
April 4, 2024 at 4:05 pm
Thank you for your guidance. I went out of town and wanted to work on queries. I traveled light so didn’t take my laptop. With what you said, I probably won’t do it anymore
April 4, 2024 at 7:41 pm
Ah, in that case, I would imagine you would have needed some sort of VPN to connect back to your SQL instance unless it is exposed to the internet. If you only have a hostname (without a domain such as "server" vs "server.company.com"), then you would definitely need a VPN. If you had an IP, and the IP is in the private IP range, then you'd need VPN. And even if you had an IP AND it is in the public IP range BUT behind a firewall, you may need a VPN.
My approach before travel is to test things like this prior to leaving the house. Grab my device, connect to a different WIFI connection (or a data connection), can I access the machine? If I can, I'm good to go. If I can't, then troubleshoot, correct, and retest until it is successful OR give up... mind you I very rarely give up.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply