

Get in touch

Download Plugin Now
  • Follow
  • Follow
WP Data Access
  • Download
  • Support
  • Features
  • Pricing
  • Documentation
    • Tool Guide
    • App Builder
    • Data Explorer
    • SQL Query Builder
    • Plugin Settings
    • Legacy Tools
    • Remote Connections
a
M
M
  • Download
  • Support
  • Features
  • Pricing
  • Documentation
    • Tool Guide
    • App Builder
    • Data Explorer
    • SQL Query Builder
    • Plugin Settings
    • Legacy Tools
    • Remote Connections
Download Plugin Now

Remote Databases

  • MySQL | MariaDB
  • Heterogeneous Connections
  • Using ODBC | JDBC
  • Connect to SQL Server
  • WordPress user ID in SQL

Premium Data Services

  • Remote wizard
  • START HERE
  • Errors and messages
  • Limitations
  • Tutorials
  • Remote Databases
    • Overview
    • SQL Server
    • PostgreSQL
    • Oracle
    • MariaDB | MySQL
  • Remote Data Files
    • Overview
    • CSV files
    • JSON files
    • MS Access
    • XML files
    • Public URL
    • Synchronization
  • Advanced features
    • Performance
    • Indexes
View Categories

Indexes

Tables created from remote database connections and remote data files are not normal database tables. These tables are depending on their remote connection or data file. Most of these tables support local indexes, except tables created from JSON and XML files. Do not create indexes on these tables. The table will no longer be accessible if you do.

When a table is queried through a remote database connection, the remote database server uses available indexes when applicable. There is usually no need to create local indexes for these tables. There are two exceptions to this rule:

  1. A local primary key is needed to enable transactions in WP Data Access.
  2. A local index might increase performance for columns used in joins.

You can join tables from different data sources. You can for example join an MS Access table, an Oracle table, and a CSV spreadsheet. Without local indexes on columns used to join these tables, the DBMS needs to load these tables entirely to perform a join. In these cases, local indexes can increase performance dramatically. Do not join large tables without local indexes! Such a query might take forever…

Tables created from a CSV file can be indexed as well. The plugin maintains these indexes automatically. It is even possible to add a primary key to these tables, which enables transaction support in WP Data Access. Table changes however are not written to the original remote data file, even if the public URL to this file remains valid. Synchronization works in one direction only.

Example CSV file with primary key and inline editing enabled #

The following screenshot demonstrates a table created from a CSV file. After loading the CSV file into the database, I added a primary key on column Empno and enabled inline editing for all columns (except the primary key which is generally not editable in WP Data Access).

WP Data Access CSV inline editing

Important #

Don’t create indexes on tables created from a JSON or XML file. The index makes your table inaccessible (removing the index will make the table accessible again).

Share This Article :
  • Facebook
  • X
  • LinkedIn
  • Pinterest
Still stuck? How can we help?

How can we help?

Updated on 2025-02-07
Performance

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Table of Contents
  • Example CSV file with primary key and inline editing enabled
  • Important
WP Data Access
  • Follow
  • Follow
Quick Links
$

Blogs

$

Tutorials

$

Demos

Get in touch
$

Premium support

$

Free support forum

$

Contact us

Resources


WordPress plugin directory



YouTube tutorials

Copyright © 2025 | All Right Reserves

We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok