The JetAttachDatabase2 function attaches a database file for use with a database instance and specifies a maximum size for that database. In order to use the database, it will need to be subsequently opened with JetOpenDatabase.
JET_ERR JET_API JetAttachDatabase2( __in JET_SESID sesid, __in const tchar* szFilename, __in const unsigned long cpgDatabaseSizeMax, __in JET_GRBIT grbit );
The database session context that will be used for the API call.
The name of the database to attach.
The maximum size, in database pages, for database. The default database page size is 4 kilobytes, which can be changed using the JetSetSystemParameter function prior to creating a database.
Passing zero means that there is no maximum enforced by the database engine.
A group of bits that contain the options to be used for this call, which include zero or more of the following:
If JET_paramEnableIndexChecking has been set, all indexes over Unicode data will be deleted. See the Remarks section for more details.
All indexes over Unicode data will be deleted, regardless of the setting of JET_paramEnableIndexChecking. See the Remarks section for more details.
Prevents modifications to the database.
Reserved for future use.
The operation completed successfully.
Attaching a database is not allowed during a backup.
The database file specified by szFilename must be writable. The Read-Only attribute must not be set, and the running process must have sufficient privileges to write to the file.
The database file is already opened by another process.
An invalid path was given in szFilename. szFilename must be non-NULL and refer to a valid path.
The database file has already been attached by a different session.
The file given in szFilename does not exist.
There is an error with the primary index. This may be from physical corruption (such as disk or memory corruption). It may also be returned when attaching a database last modified on an older operating system and the primary index is over a column with Unicode data. See the remarks for more information on indexes over Unicode data.
There is an error with a secondary index. This may be from physical corruption (such as disk or memory corruption). It may also be returned when attaching a database last modified on an older operating system and a secondary index is over a column with Unicode data. See the remarks for more information on indexes over Unicode data. Secondary indexes are completely rebuilt when a database is defragmented with an offline utility using the following command: esentutl -d.
Only a finite number of databases can be attached per instance. The limit is currently seven databases per instance.
A nonfatal warning indicating that the database file has already been attached by this session.
See JetAttachDatabase for remarks.
Requires Windows Vista, Windows XP, or Windows 2000 Professional.
Requires Windows Server 2008, Windows Server 2003, or Windows 2000 Server.
Declared in Esent.h.
Implemented as JetAttachDatabase2W (Unicode) and JetAttachDatabase2A (ANSI).