Connecting to a Local Database
March 15th, 2007
SQL is my kind of fast, powerful, geekiness. I’m forever forgetting the ins-and-outs of connecting to a local database with SQL Anywhere though, so it needs noting.
There’s a pretty comprehensive SupportWeb article that covers everything you need to know. In summary:
- for Siebel 6 use isql55.exe from the \bin directory, then username DBA and password SQL.
- for 7.0 and 7.5 use dbisqlc.exe and the same DBA/SQL.
- for 7.7 and 7.8 it’s still dbisqlc.exe but the login changes to DBA/<Enterprise Name> (in upper case).
- not sure about 8 yet…
Update: those executables are all in the client\bin directory, regardless of version.
Another login option in all versions is the username SIEBEL with the local password for the database you’re connecting to (in upper case). This can be handy if somebody’s changed the database admin password, for instance…
The Watcom-SQL variant is somewhat different from Oracle or SQL Server SQL, so it’s worth keeping the SQL Anywhere User’s Guide to hand while hacking around.
2 Comments Add your own
1. Locally unlocking a locke&hellip | March 22nd, 2007 at 9:29 pm
[...] let a second developer anywhere near it. To get around this you need to get into SQL Anywhere. Login to the second developer’s local database, then the following script will unlock the project [...]
2. Changing the Local Databa&hellip | March 29th, 2007 at 8:15 pm
[...] Connect to the local database, then run these SQL commands: [...]
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed