Skip to content
Crevia DocumentationDesign & Issuance PlatformV11
English user guide
CREVIA V11 · ENGLISH USER GUIDE

Supported Databases and Drivers

Appendices7 min read
On this page

8.1 Supported Databases and Drivers

Decide where records reside and whether continuous maintenance, photos, and concurrency are required. Database, provider, and actual identity jointly determine capabilities; a suffix alone is not a deployment plan.

8.1.1 Source Types and Uses

These types correspond to source configuration. The table is not vendor-version certification or a promise to create every server database automatically.

Source Preparation Boundary
SQLite Real file, directory/file rights, matching delivered components Suitable for evaluated local projects; a network file is not a high-concurrency server.
Access File, matching provider, password when applicable Accessibility is not provider availability; manage locks/shared writes/backups.
Excel Workbook, sheet, headers/range, compatible access environment Direct connection differs from import; Excel creation does not add photo tables and is not a complete portrait database.
MS SqlServer Host/instance, database, authentication/account Windows identity and SQL credentials are separate from CREVIA role passwords.
MySql Host, actual port, database/account Verify charset, types, and rights; a same-name database is not proof of identity.
PostgreSQL Host/port/database/account A database list aids selection, not target/schema verification.
Oracle Host/port/Service Name/account Service Name is not a local file; use administrator-provided values.
DB2 Host/port/database/account Confirm actual name and delivered driver/dependencies.
Firebird Host/port/server-side path or alias/account The server interprets its file path, not the design workstation.
ODBC Matching concrete driver and DSN/connection string An access channel, not a database; metadata/SQL/writes depend on the underlying system.
XML source Compatible file and record structure Read-oriented source, not equivalent relational maintenance; distinguish XML import.

SQLite can establish a single-machine demonstration. Existing enterprise sources need administrator-approved structure/rights. For several writers, evaluate server databases, backups, and concurrency instead of moving a single-user file onto a share.

8.1.2 Providers and Architecture

64-bit Windows can contain 32-bit drivers. Verify actual application/provider/native dependencies. Use the project's 64-bit deployment and preserve missing-component errors instead of obtaining random DLLs.

  1. Verify actual shortcut/root/version, not a different installed copy.
  2. Identify direct Access/Excel, legacy Excel, ODBC, or server access; entries can use different components.
  3. Administrators should check the required 64-bit Access Database Engine/access environment for Access/Excel/old .xls and assess Office conflicts before installation.
  4. In matching ODBC Administrator check both driver and DSN; presence of one does not establish the other.
  5. Deploy official/vendor components and test under the real business identity.

On 64-bit Windows %WINDIR%\System32\odbcad32.exe is 64-bit and %WINDIR%\SysWOW64\odbcad32.exe is 32-bit. User DSNs depend on Windows identity; system DSNs still need matching drivers. Current .xlsx exchange components differ from direct-workbook providers: successful import is not proof direct connection is ready.

Manual illustrationRequirements:

Figure 8.1-1. Show English source selection and 64-bit ODBC driver/demonstration DSN views. Distinguish type, architecture, and DSN; hide production hosts/accounts/passwords/strings.

8.1.3 Parameters and Permissions

File engines can need directory writes for locks/helper files. Explorer reading is not database writability; shares and filesystem permissions both apply to the real operator. Server settings need actual host/port/database or service/authentication. db-demo and StaffDemo are separate fictitious host/database values, not defaults. Do not expose database ports publicly for diagnosis.

Layer Verify Misconception
Network Approved route to service Web browsing proves internal connectivity.
Identity Actual account/authentication/target CREVIA admin equals database admin.
Schema Tables, fields, relationships Same database name means same structure.
Read Correct project/person scope Connection success means correct personnel.
Write Operation grants and constraints Read access implies maintenance.

Main/group SQL and interface conditions also affect counts. Diagnose empty results through 7.5 rather than granting full-database rights to experiment.

8.1.4 Standard Acceptance Procedure

This is a recommended test, not an executed site report. Use an isolated database and approved identity. Configure/test in CDPS and confirm identity; preview a known person's name, text number, date, reference, and photo; save query and entire layout and reopen. In COC test the real role's scope and approved add/edit/reread. Delete only a newly created demonstration record if deletion testing is authorized, checking related tables/photos. Repeat for actual workstation types and record versions/driver architecture/source/results.

Mark Not Tested, Pass, or Fail explicitly. Unperformed photo/write/concurrency checks are not passes. See 4.5 for configuration, Chapter 6 for deployment/backup, and 7.3 for connection faults.

8.1.5 Selection and Compatibility Limits

Assess photo volume, growth, simultaneous users, backup duration, and recovery objectives. There is no universal capacity/workstation performance promise; vendor theoretical maxima are not business-query measurements.

ODBC connectivity does not guarantee primary-key/relationship/write-target discovery. Aggregates, computed columns, complex queries, and readonly views can display without maintenance. SQL migration requires checking identifier, date, Boolean, and NULL syntax. After changing engines/providers/schema, retest queries/import/photos/reports/writeback on copies, retaining known-good deployment records rather than replacing drivers during production batches.