2011

2 Do one of the following:
■ Create a database datastore. (page 588)
■ Create an SDF or SHP data store. (page 589)
NOTE You can also delete a data store. (page 593)
Setting Up Database Users
You can use the FDO User Manager utility that comes with AutoCAD Map 3D
to set up database users for Oracle, SQL Server, PostgreSQL/PostGIS, and
MySQL.
NOTE This functionality affects geospatial feature data only. For information about
linking records in an external database to objects in a drawing, see
Overview of
Linking Database Records to Objects
(page 522). For information about managing
drawing objects and drawing files, see
Overview of Setting Up Your Map File (page
140).
For an Oracle data store (page 2059), AutoCAD Map 3D separates the concept
of the Oracle user who owns the
schema (page 2073) from the Oracle user who
accesses the schema.
When you create a new Oracle data store in AutoCAD Map 3D (page 586),
AutoCAD Map 3D automatically creates a new corresponding Oracle user who
is the owner of that data. For example, creating a data store called mycitydb
creates an Oracle user called mycitydb. However, you must also create separate
Oracle users for the purpose of accessing the data store. These Oracle users
match the end users who will access the data. For example, if an end-user
named JSmith will be connecting to the new data store, you create an Oracle
user with that name and grant him access to the new data store. This allows
different users who access the same data to have different privileges.
To access data that resides in a relational database, AutoCAD Map 3D requires
that database users have certain privileges. Use FDO User Manager to add a
new user with the appropriate roles. FDO User Manager is a command-line
utility that lets you manage database users and accounts consistently across
database management systems.
When you create users for an Oracle instance with the FDO User Manager
tool, those users have the privileges that support data access operations for
that data store. If you access the data store as an Oracle user who was not
created using FDO User Manager, the Database Administrator must ensure
584 | Chapter 4 Managing Data