Give the new user permission to connect and to create their own tables etc.
Specific to SQLite
none
DB2
Give the new user permission to connect and to create their own tables etc.
Specific to DB2
Create a user from the operating system. Have that user run the command:
. /home/db2inst1/sqllib/db2profile
as part of the .bashrc (or whatever).
MS Access
Give the new user permission to connect and to create their own tables etc.
Specific to MS Access
Access is a single user system. (Please email me if you know otherwise.)
PostgreSQL
Give the new user permission to connect and to create their own tables etc.
Specific to PostgreSQL
If scott is the name of a Unix account there is no problem - otherwise you must add the line local template1 password
to the file /usr/lib/postgres/data/pg_hba.conf this allows any user with a postgres account to connect to database template1.
Oracle
Give the new user permission to connect and to create their own tables etc.
Specific to Oracle
You should specify the "tablespace" - if you don't it defaults to SYS which causes a whole world of pain.
The CONNECT and RESOURCE grants permit users to connect to the system and to create stuff.
MS SQL Server
Give the new user permission to connect and to create their own tables etc.
Specific to MS SQL Server
none
MySQL
Give the new user permission to connect and to create their own tables etc.
Specific to MySQL
Sybase
Give the new user permission to connect and to create their own tables etc.
Specific to Sybase
none
Mimer SQL
Give the new user permission to connect and to create their own tables etc.
Specific to Mimer SQL
An IDENT is a user. A DATABANK corresponds to a file where the data is actually stored. Users normally have a SCHEMA - this is created as the user is created.