Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » UltraLite - Database Management and Reference » Connecting to an UltraLite Database » Introduction to UltraLite database connections

List of UltraLite database connection parameters Next Page

The role of user authentication

In UltraLite, you cannot disable authentication. A successful connection requires that a user be authenticated. Unlike SQL Anywhere, UltraLite database users are created and managed solely for the purposes of authentication—and not for the purposes of object ownership. Once a user authenticates and connects to the database, the user has unrestricted access to everything in that database—including schema data.

You can only add or modify UltraLite users from an existing connection. Therefore, any changes to your UltraLite user-base can only occur after you have connected with a valid UID and PWD.

If this is your first time connecting, the UID and PWD required are the same values set when you first created the database. If you did not set an initial user, then you must authenticate with the defaults of UID=DBA and PWD=sql.

Bypassing authentication

While you may not be able to disable authentication, you can bypass it simply by using UltraLite defaults both when you create and connect to the database.

By not supplying both the UID and the PWD parameters—irrespective of the connection method you use—UltraLite will then always assumes the defaults of UID=DBA and PWD=sql.

To bypass authentication in UltraLite
  1. Do not set a UID and PWD parameters when you create a database.

  2. Do not delete or modify the default user in your UltraLite database.

  3. Do not set a UID and PWD parameters when you connect to the database you have created.

See also

Interpreting user ID and password combinations