Is it possible to connect to the derby database through odbc on a windows 10 machine? I have the jdbc-odbc bridge from Java 7. Found this:
Derby network server
The Derby network server provides traditional client/server access to the Derby
engine. The network server lets clients connect over TCP/IP using a subset of
the DRDA protocol. The network server supports connections from networked JDBC,
ODBC/CLI, Perl, and PHP clients.
But can’t find any examples or instructions on how to connect with ODBC/CLI
Related
Usually, we connect ODBC driver using BI applications on our local machine,
Just imagine I created an ODBC driver for PostgreSQL in the remote machine at my home (Windows 10), I want to connect that ODBC driver (remotely) from my office workstation (windows 8) using any BI application (such as Excel, power Bi). For this, I have to find the solution to update the driver for the remote concept. so that please refer any technology that does this.
Note: the PostgreSQL can be on any machine like the same windows 10 machine or any other server machine.
Reference
Can SQL Server Express be accessed from another computer running SQL Server Management Studio across the network? Assuming there are no network firewalls etc.
Yes, you can. But remember that you must accept open to remote or tcp/ip connections
I have SQL server running on a legacy Windows 2003 box on IP address 192.168.2.240. There seems to be a reference to the server with some old connection strings for a web application. I'm merely using it for comparison purposes because we just upgraded to Windows Server 2008, .NET 4.0 and Enterprise Library 5.0. The server is referenced with "SQL01" not the IP address. On the network where this IP address resides, I can ping "SQL01", but when I VPN to that network, I cannot. Why wouldn't this work over a VPN? This is a legacy server, and I don't know how it was setup. If anyone can explain where this name is configured, and how I can connect (or ping) "SQL01" instead of using the IP address, I'd like to be enlightened.
Try looking in your hosts file.
I have three systems, Sql Server Express only on one. I would access sql server on main pc from the other two to enter data into a database using a winform application. all three pcs are on LAN. what do i have to do establish connection with sql server on the main pc from the other two pcs? That is, how do i network my sql server express so that it is installed only on one machine but used by two other machines also. What protocols would i have to turn on or off?
All 3 pcs are in a same room. Also, sql remote connection means connecting via internet?
I'm trying to connect from my ms windows 7 via the odbc administrator to a remote
sybase sqlanywhere 11 database server.
But I get not connection, I'm not sure which configure option I have to specify.
server-name = ip address of remote database server?
startline ?
portnummer ?
Thank you, best regards, Alex
By default the SQL Anywhere server process dbsrv#.exe listens for incoming connections on port 2638.
Make sure your firewall allows outbound connections to that port.
Assuming you have a database running on your server as follows:
-x tcpip
-n my_server_name
"[DIR]\database_main_file.db" -n my_database_name
The server will broadcast on the tcp/ip layer on the default port (2638) under the name "my_server_name" and the database will be accessible under the name "my_database_name" via ODBC
Creating an ODBC entry for your new database to connect from a client (adjust for Windows 7)
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\myodbcentry]
"Driver"="C:\\PROGRA~1\\SQLANY~1\\Bin32\\dbodbc11.dll"
"DatabaseName"="my_database_name"
"ServerName"="my_server_name"
"LINKS"="TCPIP(IP=SERVER_IP_ADDRESS;PORT=2638)"
There are other parameters available for LINKS (HOST, etc). Take a look at http://dcx.sybase.com/index.html#1101en/dbadmin_en11/da-using-tcpip.html
I've seen some rare issues with UDP broadcast packets. See the docs at
http://dcx.sybase.com/1101en/dbadmin_en11/broadcastlistener-connection-conparm.html and check with your network administrator.
You can also use the dbping.exe utility to troubleshoot networking issues.
BTW, you may want to cross-post your question at http://sqla.stackexchange.com. It's full of SQL Anywhere buffs