Connection strings for Sybase Adaptive

ASE ADO.NET Data Provider

Type .NET Framework Class Library
Usage Sybase.Data.AseClient.AseConnection
Manufacturer Sybase


Data Source='myASEserver';Port=5000;Database=myDataBase;Uid=myUsername;Pwd=myPassword;

Using the sql.ini file

If the server isn't aliased, you have to use the ip address and port number in the connection string, not ideal as these may change occassionally. Installing sybase on a machine, you will have a "sql.ini" file that maps an alias name to an ip address and a port. That file can be rolled out to all users, and the sql.ini updated when necessary. Use the following connection string to force the AseConnection object to use the interface file.


Adaptive Server Anywhere OLE DB Provider

Type OLE DB Provider
Usage Provider=ASAProv
Manufacturer Sybase


Provider=ASAProv;Data source=myASA;



Use this when connecting to a server located on the other side of a router. Without the Links=tcpip(Host=servername) the error "Server could not be found" can arise when connecting.


Adaptive Server Anywhere ODBC Driver

Type ODBC Driver
Usage Driver=Adaptive Server Anywhere 7.0
Manufacturer Sybase


Driver=Adaptive Server Anywhere 7.0;ENG=server.database_name;UID=myUsername;

Specific port

Driver=Adaptive Server Anywhere 7.0;ENG=server.database_name;UID=myUsername;

Multiple servers

Driver=Adaptive Server Anywhere 7.0;ENG=server.database_name;UID=myUsername;

Multiple servers with different TCP/IP ports

Driver=Adaptive Server Anywhere 7.0;ENG=server.database_name;UID=myUsername;

Sybase ASE OLE DB Provider

Type OLE DB Provider
Usage Provider=ASEOLEDB
Manufacturer Sybase

With Data Source .IDS file

Provider=Sybase ASE OLE DB Provider;Data source=myASE;

Note that you must create a Data Source .IDS file using the Sybase Data Administrator. These .IDS files resemble ODBC DSNs.


Adaptive Server Enterprise (ASE) alternative 1

User Id=myUsername;Password=myPassword;

Some reports on problem using the above one, try the following as an alternative.


Adaptive Server Enterprise (ASE) alternative 2

Provider=Sybase.ASEOLEDBProvider;Server Name=myASEserver,5000;
Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;

Some other reports on problem using the above one, try the following as an alternative


Adaptive Server Enterprise (ASE) 12.5

Provider=Sybase.ASEOLEDBProvider.2;Server Name=myASEserver;Server Port Address=5000;
Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;

This one works only from Open Client 12.5 where the server port number feature works, allowing fully qualified connection strings to be used without defining any .IDS Data Source files.


Adaptive Server Enterprise (ASE) 15.0

Provider=ASEOLEDB;Data Source=myASEserver:5000;Catalog=myDataBase;User Id=myUsername;

Adaptive Server Enterprise (ASE) 15.0 alternative

This one is included because of reported problems with using the "Catalog" key which was solved by using the 12.5 syntax key "Initial Catalog" instead.

Provider=ASEOLEDB;Data Source=myASEserver:5000;Initial Catalog=myDataBase;
User Id=myUsername;Password=myPassword;

.NET Framework Data Provider for OLE DB

Type .NET Framework Wrapper Class Library
Usage System.Data.OleDb.OleDbConnection
Manufacturer Microsoft

Use an OLE DB provider from .NET

Provider=any oledb provider's name;OledbKey1=someValue;OledbKey2=someValue;

See the respective OLEDB provider's connection strings options. The .net OleDbConnection will just pass on the connection string to the specified OLEDB provider. Read more here.


Adaptive Server Enterprise ODBC driver

Type ODBC Driver
Usage Driver={Adaptive Server Enterprise}
Manufacturer Sybase

Adaptive Server Enterprise 15.0

Driver={Adaptive Server Enterprise};app=myAppName;server=myServerAddress;

The key "app" is optional


Standard Sybase System 12 Enterprise Open Client

Driver={SYBASE ASE ODBC Driver};Srvr=myServerAddress;Uid=myUsername;Pwd=myPassword;

Standard Sybase System 12.5 Enterprise Open Client

Driver={SYBASE ASE ODBC Driver};NA=Hostname,Portnumber;Uid=myUsername;Pwd=myPassword;

TDS based ODBC driver (from Sybase OCS 12.5)

Driver={Sybase ASE ODBC Driver};NetworkAddress=myServerAddress,5000;Db=myDataBase;

Standard Sybase System 11

Driver={SYBASE SYSTEM 11};Srvr=myServerAddress;Uid=myUsername;Pwd=myPassword;

Intersolv 3.60

Type ODBC Driver
Usage Driver={INTERSOLV 3.60 32-BIT Sybase}
Manufacturer DataDirect Technologies


Driver={INTERSOLV 3.60 32-BIT Sybase};Srvr=myServerAddress;Database=myDataBase;

Intersolv 3.10

Type ODBC Driver
Usage Driver={INTERSOLV 3.10 32-BIT Sybase}
Manufacturer DataDirect Technologies

Intersolv 3.10

Driver={INTERSOLV 3.10 32-BIT Sybase};Srvr=myServerAddress;Uid=myUsername;

Sybase SQL Anywhere (former Watcom SQL) ODBC driver

Type ODBC Driver
Usage Driver=Sybase SQL Anywhere 5.0
Manufacturer Sybase

Default local database engine

Driver={Sybase SQL Anywhere 5.0};DefaultDir=c:\dbfolder\;Dbf=c:\mydatabase.db;

The empty DSN parameter could be critical if experiencing error 7778.

Remember to start the connection string with "odbc:" if you are using PHP PDO_ODBC


Database engine not running

Driver={Sybase SQL Anywhere 5.0};Uid=myUsername;Pwd=myPassword;
DatabaseSwitches=-commandSwitch1 -commandSwitch2;DatabaseFile=c:\pb\ex\psdemodb.db;AutoStop=NO;

If AutoStop is set to YES then the database is unloaded automatically as soon as there are no more open connections to it.

When the engine starts the database specified by DatabaseFile, the engine will use the supplied DatabaseSwitches as command line options to determine startup options for the database. The Sybase manual contains a List of DatabaseSwitch values.


.NET Framework Data Provider for ODBC

Type .NET Framework Wrapper Class Library
Usage System.Data.Odbc.OdbcConnection
Manufacturer Microsoft

Use an ODBC driver from .NET

Driver={any odbc driver's name};OdbcKey1=someValue;OdbcKey2=someValue;

See the respective ODBC driver's connection strings options. The .net OdbcConnection will just pass on the connection string to the specified ODBC driver. Read more here.