in reply to Connect to remote MSSQL database with DBD-ODBC?

One likely major obstacle is that if their network admins have any clue whatsoever, your traffic is being blocked at their perimeter by a firewall. If not, their database is likely compromised anyway.

That said, why on Earth would you want to even consider connecting with plaintext to a customer database over the internet? Has anyone in your legal department (or theirs) reviewed the content for potential regulatory problems?

Get your network team talking to theirs about some method of an encrypted communications tunnel between these two servers. If you don't need the data in real time, you could also exchange it as an encrypted file.


The intelligent reader will judge for himself. Without examining the facts fully and fairly, there is no way of knowing whether vox populi is really vox dei, or merely vox asinorum. — Cyrus H. Gordon
  • Comment on Re: Connect to remote MSSQL database with DBD-ODBC?

Replies are listed 'Best First'.
Re^2: Connect to remote MSSQL database with DBD-ODBC?
by FinnR (Novice) on Dec 14, 2005 at 19:03 UTC
    Thanks - I'll forward your input to someone else to see if they've thought of it. The programming is still on the testing stage. The code I posted has only been used with a test MSSQL installation on a remote demo server so far.

    The idea was to get the basics to work here first, and then take the next step by connecting to the customer's server (with a none default port - not 1433, and with restrictions on which IPs are able to connect. The network part should be in good hands with the customer's network admin. Thanks again!