Informix slower than MS Access ? 
Author Message
 Informix slower than MS Access ?

Hello,

is there any help for me and my informix server ???

I have a performance problem with Informix IDS 7.30 UC5 on a SUN Solaris
5.5.1 (one processor with 512 MByte RAM)

There is a table with 14 columns and 1.600.000 Rows.

My Sql-Select is :

SELECT lager, art_nr, SUM(menge)
FROM lag_bew
WHERE art_nr > 99000000
GROUP BY lager, art_nr
HAVING SUM(menge) > 10000
ORDER BY art_nr

The result contains 27 rows and takes 45 seconds ;-(.

The same select on an NT-Server (smaller than the SUN) with Mr. Gates's
Access takes only 25
seconds (Thats true !).

Informix does a sequential scan on the table an needs a temporary file for
group and order by.
The table has only 2 extents.

If i create a index such as (art_nr, lager) or  (lager, art_nr)  the select
takes over one minute (Thats true also !).
The explain shows that Informix use this index and need no temporary file.

The database has no transactions, the lock mode of the table is page and if
i lock the table in exclusive mode the select is only 2 seconds faster.

Now to the server:

I'm using two cooked files, one for the rootdbs and one for the datadbs on
the same disc-device.
Does the performance increase so much if I'm using raw devices ?

Here is my $ONCONFIG-File:

#**************************************************************************
#
#      INFORMIX SOFTWARE, INC.
#
#  Title: onconfig.std
#  Description: Informix Dynamic Server Configuration Parameters
#
#**************************************************************************

# Root Dbspace Configuration

ROOTNAME        rootdbs         # Root dbspace name
ROOTPATH        /DB001/dbs/root_dbs # Path for device containing root
dbspace
ROOTOFFSET      0               # Offset of root dbspace into device
(Kbytes)
ROOTSIZE        400000          # Size of root dbspace (Kbytes)

# Disk Mirroring Configuration Parameters

MIRROR          0               # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH                      # Path for device containing mirrored root
MIRROROFFSET    0               # Offset into mirrored device (Kbytes)

# Physical Log Configuration

PHYSDBS         rootdbs         # Location (dbspace) of physical log
PHYSFILE        2000            # Physical log file size (Kbytes)

# Logical Log Configuration

LOGFILES        24              # Number of logical log files
LOGSIZE         8000            # Logical log size (Kbytes)

# Diagnostics

MSGPATH         /DB001/informix/online.log # System message log file path
CONSOLE         /dev/console    # System console message path
ALARMPROGRAM    /DB001/informix/etc/log_full.sh # Alarm program path
SYSALARMPROGRAM /DB001/informix/etc/evidence.sh # System Alarm program path
TBLSPACE_STATS  1

# System Archive Tape Device

TAPEDEV         /dev/null       # Tape device path
TAPEBLK         16              # Tape block size (Kbytes)
TAPESIZE        10240           # Maximum amount of data to put on tape
(Kbytes)

# Log Archive Tape Device

LTAPEDEV        /dev/null       # Log tape device path
LTAPEBLK        16              # Log tape block size (Kbytes)
LTAPESIZE       10240           # Max amount of data to put on log tape
(Kbytes)

# Optical

STAGEBLOB                       # Informix Dynamic Server/Optical staging
area

# System Configuration

SERVERNUM       1               # Unique id corresponding to a Dynamic
Server instance
DBSERVERNAME    db_ows          # Name of default database server
DBSERVERALIASES db_ows_shm      # List of alternate dbservernames
NETTYPE         tlitcp,1,,      # Configure poll thread(s) for nettype
NETTYPE         ipcshm,1,,      # Configure poll thread(s) for nettype
DEADLOCK_TIMEOUT 60              # Max time to wait of lock in distributed
env.
RESIDENT        0               # Forced residency flag (Yes = 1, No = 0)

MULTIPROCESSOR  0               # 0 for single-processor, 1 for
multi-processor
NUMCPUVPS       1               # Number of user (cpu) vps
SINGLE_CPU_VP   1               # If non-zero, limit number of cpu vps to
one

NOAGE           0               # Process aging
AFF_SPROC       0               # Affinity start processor
AFF_NPROCS      0               # Affinity number of processors

# Shared Memory Parameters

LOCKS           150000      # Maximum number of locks
BUFFERS         20000           # Maximum number of shared buffers
NUMAIOVPS                       # Number of IO vps
PHYSBUFF        32              # Physical log buffer size (Kbytes)
LOGBUFF         16              # Logical log buffer size (Kbytes)
LOGSMAX         50              # Maximum number of logical log files
CLEANERS        2               # Number of buffer cleaner processes
SHMBASE         0xa000000         # Shared memory base address
SHMVIRTSIZE     8000            # initial virtual shared memory segment size
SHMADD          8192            # Size of new shared memory segments
(Kbytes)
SHMTOTAL        0               # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL       120             # Check point interval (in sec)
LRUS            8              # Number of LRU queues
LRU_MAX_DIRTY   10              # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY   5              # LRU percent dirty end cleaning limit
LTXHWM          50              # Long transaction high water mark
percentage
LTXEHWM         60              # Long transaction high water mark
(exclusive)
TXTIMEOUT       0x12c             # Transaction timeout (in sec)
STACKSIZE       32              # Stack size (Kbytes)

# System Page Size
# BUFFSIZE - Dynamic Server no longer supports this configuration parameter.
#            To determine the page size used by Dynamic Server on your
platform
#            see the last line of output from the command, 'onstat -b'.

# Recovery Variables
# OFF_RECVRY_THREADS:
# Number of parallel worker threads during fast recovery or an offline
restore.
# ON_RECVRY_THREADS:
# Number of parallel worker threads during an online restore.

OFF_RECVRY_THREADS 10              # Default number of offline worker
threads
ON_RECVRY_THREADS 1               # Default number of online worker threads

# Data Replication Variables
# DRAUTO: 0 manual, 1 retain type, 2 reverse type
DRAUTO          0               # DR automatic switchover
DRINTERVAL      30              # DR max time between DR buffer flushes (in
sec)
DRTIMEOUT       30              # DR network timeout (in sec)
DRLOSTFOUND     /DB001/informix/etc/dr.lostfound # DR lost+found file path

# CDR Variables
CDR_LOGBUFFERS  2048            # size of log reading buffer pool (Kbytes)
CDR_EVALTHREADS 1,2             # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT  5               # DS lockwait timeout (seconds)
CDR_QUEUEMEM    4096            # Maximum amount of memory for any CDR queue
(Kbytes)

# Backup/Restore variables
BAR_ACT_LOG     /tmp/bar_act.log
BAR_MAX_BACKUP  0
BAR_RETRY       1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31

# Informix Storage Manager variables
ISM_DATA_POOL   ISMData         # If the data pool name is changed, be sure
to
    # update $INFORMIXDIR/bin/onbar.  Change to
    # ism_catalog -create_bootstrap -pool <new name>
ISM_LOG_POOL    ISMLogs

# Read Ahead Variables
RA_PAGES                        # Number of pages to attempt to read ahead
RA_THRESHOLD                    # Number of pages left before next group

# DBSPACETEMP:
# Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces
# that the Dynamic Server SQL Engine will use to create temp tables etc.
# If specified it must be a colon separated list of dbspaces that exist
# when the Dynamic Server system is brought online.  If not specified, or if
# all dbspaces specified are invalid, various ad hoc queries will create
# temporary files in /tmp instead.

DBSPACETEMP                     # Default temp dbspaces

# DUMP*:
# The following parameters control the type of diagnostics information which
# is preserved when an unanticipated error condition (assertion failure)
occurs
# during Dynamic Server operations.
# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.

DUMPDIR         /tmp            # Preserve diagnostics in this directory
DUMPSHMEM       1               # Dump a copy of shared memory
DUMPGCORE       0               # Dump a core image using 'gcore'
DUMPCORE        0               # Dump a core image (Warning:this aborts
Dynamic Server)
DUMPCNT         1               # Number of shared memory or gcore dumps for
    # a single user's session

FILLFACTOR      90              # Fill factor for building indexes

# method for Dynamic Server to use when determining current time
USEOSTIME       0               # 0: use internal time(fast), 1: get time
from OS(slow)

# Parallel Database Queries (pdq)
MAX_PDQPRIORITY 100             # Maximum allowed pdqpriority
DS_MAX_QUERIES                  # Maximum number of decision support queries
DS_TOTAL_MEMORY                 # Decision support memory (Kbytes)
DS_MAX_SCANS    1048576         # Maximum number of decision support scans
DATASKIP        off             # List of dbspaces to skip

# OPTCOMPIND
# 0 => Nested loop joins will be preferred (where
#      possible) over sortmerge joins and hash joins.
# 1 => If the transaction isolation mode is not
#      "repeatable read", optimizer behaves as in (2)
#      below.  Otherwise it behaves as in (0) above.
# 2 => Use costs regardless of the transaction isolation
#      mode.  Nested loop joins are not necessarily
#      preferred.  Optimizer bases its decision purely
#      on costs.
OPTCOMPIND      0               # To hint the optimizer

ONDBSPACEDOWN   1               # Dbspace down option: 0 = CONTINUE, 1 =
ABORT, 2 = WAIT
LBU_PRESERVE    0               # Preserve last log for log backup
OPCACHEMAX      0               # Maximum optical cache size (Kbytes)

# HETERO_COMMIT (Gateway participation in distributed transactions)
# 1 => Heterogeneous Commit is enabled
# 0 (or any other value) => Heterogeneous Commit is disabled
HETERO_COMMIT   0

# ...

read more »



Wed, 18 Jun 1902 08:00:00 GMT
 Informix slower than MS Access ?


Quote:

>is there any help for me and my informix server ???

Yep.

Quote:
>I have a performance problem with Informix IDS 7.30 UC5 on a SUN Solaris
>5.5.1 (one processor with 512 MByte RAM)

>There is a table with 14 columns and 1.600.000 Rows.

>My Sql-Select is :

>SELECT lager, art_nr, SUM(menge)
>FROM lag_bew
>WHERE art_nr > 99000000
>GROUP BY lager, art_nr
>HAVING SUM(menge) > 10000
>ORDER BY art_nr

>The result contains 27 rows and takes 45 seconds ;-(.

>The same select on an NT-Server (smaller than the SUN) with Mr. Gates's
>Access takes only 25
>seconds (Thats true !).

>Informix does a sequential scan on the table an needs a temporary file for
>group and order by.
>The table has only 2 extents.

>If i create a index such as (art_nr, lager) or  (lager, art_nr)  the select
>takes over one minute (Thats true also !).
>The explain shows that Informix use this index and need no temporary file.

>The database has no transactions, the lock mode of the table is page and if
>i lock the table in exclusive mode the select is only 2 seconds faster.

>Now to the server:

>I'm using two cooked files, one for the rootdbs and one for the datadbs on
>the same disc-device.
>Does the performance increase so much if I'm using raw devices ?

>Here is my $ONCONFIG-File:

[SNIP]

>WHAT CAN I DO ?????

UPDATE STATISTICS.

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



Wed, 18 Jun 1902 08:00:00 GMT
 Informix slower than MS Access ?


Quote:
>UPDATE STATISTICS.

I've already done that...

Thanx again...

Sven



Wed, 18 Jun 1902 08:00:00 GMT
 Informix slower than MS Access ?

Quote:


>>UPDATE STATISTICS.

>I've already done that...

>Thanx again...

>Sven

You don't mention a temporary dataspace nor what your buffers are set at.
I would consider a temporary dataspace, otherwise Informix (as far as I
understand it) will use temporary files, thereby adding to the overhead,
since it has to create files, etc. etc., whereas a temporary dataspace would
avoid those headaches.

If buffers are too small, your hit rates will be too low (do onstat -p
before and after transaction).  Memory's cheap, use it.....

As one IMS/DB instructor once told me, "the only good I/O is NO I/O".



Wed, 18 Jun 1902 08:00:00 GMT
 Informix slower than MS Access ?
How much memory did your NT have?  62M ?

You're limiting the Informix Engine to 20,000 buffers.  That means that you are
limiting the total memory space for tables to 40 Meg.  With a 512 MB system, you
probably would want to set this to 150,000.

Access works by "loading" the entire table into memory when the table is open.
You could do the same thing by increasing the buffer pool size drastically and
making the table into a memory resident table.

Quote:

> Hello,

> is there any help for me and my informix server ???

> I have a performance problem with Informix IDS 7.30 UC5 on a SUN Solaris
> 5.5.1 (one processor with 512 MByte RAM)

> There is a table with 14 columns and 1.600.000 Rows.

> My Sql-Select is :

> SELECT lager, art_nr, SUM(menge)
> FROM lag_bew
> WHERE art_nr > 99000000
> GROUP BY lager, art_nr
> HAVING SUM(menge) > 10000
> ORDER BY art_nr

> The result contains 27 rows and takes 45 seconds ;-(.

> The same select on an NT-Server (smaller than the SUN) with Mr. Gates's
> Access takes only 25
> seconds (Thats true !).

> Informix does a sequential scan on the table an needs a temporary file for
> group and order by.
> The table has only 2 extents.

> If i create a index such as (art_nr, lager) or  (lager, art_nr)  the select
> takes over one minute (Thats true also !).
> The explain shows that Informix use this index and need no temporary file.

> The database has no transactions, the lock mode of the table is page and if
> i lock the table in exclusive mode the select is only 2 seconds faster.

> Now to the server:

> I'm using two cooked files, one for the rootdbs and one for the datadbs on
> the same disc-device.
> Does the performance increase so much if I'm using raw devices ?

> Here is my $ONCONFIG-File:

> #**************************************************************************
> #
> #      INFORMIX SOFTWARE, INC.
> #
> #  Title: onconfig.std
> #  Description: Informix Dynamic Server Configuration Parameters
> #
> #**************************************************************************

> # Root Dbspace Configuration

> ROOTNAME        rootdbs         # Root dbspace name
> ROOTPATH        /DB001/dbs/root_dbs # Path for device containing root
> dbspace
> ROOTOFFSET      0               # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE        400000          # Size of root dbspace (Kbytes)

> # Disk Mirroring Configuration Parameters

> MIRROR          0               # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH                      # Path for device containing mirrored root
> MIRROROFFSET    0               # Offset into mirrored device (Kbytes)

> # Physical Log Configuration

> PHYSDBS         rootdbs         # Location (dbspace) of physical log
> PHYSFILE        2000            # Physical log file size (Kbytes)

> # Logical Log Configuration

> LOGFILES        24              # Number of logical log files
> LOGSIZE         8000            # Logical log size (Kbytes)

> # Diagnostics

> MSGPATH         /DB001/informix/online.log # System message log file path
> CONSOLE         /dev/console    # System console message path
> ALARMPROGRAM    /DB001/informix/etc/log_full.sh # Alarm program path
> SYSALARMPROGRAM /DB001/informix/etc/evidence.sh # System Alarm program path
> TBLSPACE_STATS  1

> # System Archive Tape Device

> TAPEDEV         /dev/null       # Tape device path
> TAPEBLK         16              # Tape block size (Kbytes)
> TAPESIZE        10240           # Maximum amount of data to put on tape
> (Kbytes)

> # Log Archive Tape Device

> LTAPEDEV        /dev/null       # Log tape device path
> LTAPEBLK        16              # Log tape block size (Kbytes)
> LTAPESIZE       10240           # Max amount of data to put on log tape
> (Kbytes)

> # Optical

> STAGEBLOB                       # Informix Dynamic Server/Optical staging
> area

> # System Configuration

> SERVERNUM       1               # Unique id corresponding to a Dynamic
> Server instance
> DBSERVERNAME    db_ows          # Name of default database server
> DBSERVERALIASES db_ows_shm      # List of alternate dbservernames
> NETTYPE         tlitcp,1,,      # Configure poll thread(s) for nettype
> NETTYPE         ipcshm,1,,      # Configure poll thread(s) for nettype
> DEADLOCK_TIMEOUT 60              # Max time to wait of lock in distributed
> env.
> RESIDENT        0               # Forced residency flag (Yes = 1, No = 0)

> MULTIPROCESSOR  0               # 0 for single-processor, 1 for
> multi-processor
> NUMCPUVPS       1               # Number of user (cpu) vps
> SINGLE_CPU_VP   1               # If non-zero, limit number of cpu vps to
> one

> NOAGE           0               # Process aging
> AFF_SPROC       0               # Affinity start processor
> AFF_NPROCS      0               # Affinity number of processors

> # Shared Memory Parameters

> LOCKS           150000      # Maximum number of locks
> BUFFERS         20000           # Maximum number of shared buffers
> NUMAIOVPS                       # Number of IO vps
> PHYSBUFF        32              # Physical log buffer size (Kbytes)
> LOGBUFF         16              # Logical log buffer size (Kbytes)
> LOGSMAX         50              # Maximum number of logical log files
> CLEANERS        2               # Number of buffer cleaner processes
> SHMBASE         0xa000000         # Shared memory base address
> SHMVIRTSIZE     8000            # initial virtual shared memory segment size
> SHMADD          8192            # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL        0               # Total shared memory (Kbytes). 0=>unlimited
> CKPTINTVL       120             # Check point interval (in sec)
> LRUS            8              # Number of LRU queues
> LRU_MAX_DIRTY   10              # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY   5              # LRU percent dirty end cleaning limit
> LTXHWM          50              # Long transaction high water mark
> percentage
> LTXEHWM         60              # Long transaction high water mark
> (exclusive)
> TXTIMEOUT       0x12c             # Transaction timeout (in sec)
> STACKSIZE       32              # Stack size (Kbytes)

> # System Page Size
> # BUFFSIZE - Dynamic Server no longer supports this configuration parameter.
> #            To determine the page size used by Dynamic Server on your
> platform
> #            see the last line of output from the command, 'onstat -b'.

> # Recovery Variables
> # OFF_RECVRY_THREADS:
> # Number of parallel worker threads during fast recovery or an offline
> restore.
> # ON_RECVRY_THREADS:
> # Number of parallel worker threads during an online restore.

> OFF_RECVRY_THREADS 10              # Default number of offline worker
> threads
> ON_RECVRY_THREADS 1               # Default number of online worker threads

> # Data Replication Variables
> # DRAUTO: 0 manual, 1 retain type, 2 reverse type
> DRAUTO          0               # DR automatic switchover
> DRINTERVAL      30              # DR max time between DR buffer flushes (in
> sec)
> DRTIMEOUT       30              # DR network timeout (in sec)
> DRLOSTFOUND     /DB001/informix/etc/dr.lostfound # DR lost+found file path

> # CDR Variables
> CDR_LOGBUFFERS  2048            # size of log reading buffer pool (Kbytes)
> CDR_EVALTHREADS 1,2             # evaluator threads (per-cpu-vp,additional)
> CDR_DSLOCKWAIT  5               # DS lockwait timeout (seconds)
> CDR_QUEUEMEM    4096            # Maximum amount of memory for any CDR queue
> (Kbytes)

> # Backup/Restore variables
> BAR_ACT_LOG     /tmp/bar_act.log
> BAR_MAX_BACKUP  0
> BAR_RETRY       1
> BAR_NB_XPORT_COUNT 10
> BAR_XFER_BUF_SIZE 31

> # Informix Storage Manager variables
> ISM_DATA_POOL   ISMData         # If the data pool name is changed, be sure
> to
>     # update $INFORMIXDIR/bin/onbar.  Change to
>     # ism_catalog -create_bootstrap -pool <new name>
> ISM_LOG_POOL    ISMLogs

> # Read Ahead Variables
> RA_PAGES                        # Number of pages to attempt to read ahead
> RA_THRESHOLD                    # Number of pages left before next group

> # DBSPACETEMP:
> # Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces
> # that the Dynamic Server SQL Engine will use to create temp tables etc.
> # If specified it must be a colon separated list of dbspaces that exist
> # when the Dynamic Server system is brought online.  If not specified, or if
> # all dbspaces specified are invalid, various ad hoc queries will create
> # temporary files in /tmp instead.

> DBSPACETEMP                     # Default temp dbspaces

> # DUMP*:
> # The following parameters control the type of diagnostics information which
> # is preserved when an unanticipated error condition (assertion failure)
> occurs
> # during Dynamic Server operations.
> # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.

> DUMPDIR         /tmp            # Preserve diagnostics in this directory
> DUMPSHMEM       1               # Dump a copy of shared memory
> DUMPGCORE       0               # Dump a core image using 'gcore'
> DUMPCORE        0               # Dump a core image (Warning:this aborts
> Dynamic Server)
> DUMPCNT         1               # Number of shared memory or gcore dumps for
>     # a single user's session

> FILLFACTOR      90              # Fill factor for building indexes

> # method for Dynamic Server to use when determining current time
> USEOSTIME       0               # 0: use internal time(fast), 1: get time
> from OS(slow)

> # Parallel Database Queries (pdq)
> MAX_PDQPRIORITY 100             # Maximum allowed pdqpriority
> DS_MAX_QUERIES                  # Maximum number of decision support queries
> DS_TOTAL_MEMORY                 # Decision support memory (Kbytes)
> DS_MAX_SCANS    1048576         # Maximum number of decision support scans
> DATASKIP        off             # List of dbspaces to skip

> # OPTCOMPIND
> # 0 => Nested

...

read more »



Wed, 18 Jun 1902 08:00:00 GMT
 Informix slower than MS Access ?
Hi,

first of all, writes to cooked files are up to 10 times slower
than to raw devices. Your query will create a temporary file,
even if you create an index on the column art_nr. Therefore
I expect writes to your /tmp directory. You didn't set DBSPACETEMP,
so the temporary file will be created in your /tmp directory.

Do the following:

create index lag_bew01 on lag_bew( art_nr ) in datdbs;
update statistics for table lag_bew;

Now, force the system not to create temporary file by
setting your DS_TOTAL_MEMORY configuration parameter to
an appropriate value ( depends on the size of the group
by result ).

i.e.

DS_TOTAL_MEMORY 40000

and modify your Read-Ahead Pages parameter:

RA_PAGES  32
RA_THRESHOLD 16

re-start your Informix server and insert the
pdq-statement.

set pdqpriority 90;

 SELECT lager, art_nr, SUM(menge)
 FROM lag_bew
 WHERE art_nr > 99000000
 GROUP BY lager, art_nr
 HAVING SUM(menge) > 10000
 ORDER BY art_nr;

If your query will still take longer than the one running
on the Access system, measure your disk speed on the SUN platform.
Additionally send us the ouput of "oncheck -pT yourdatabase:lag_bew".

Best regards,

Stefan Weideneder

PS: Wir k?nnen uns auch auf Deutsch weiter unterhalten.

Quote:

> Hello,

> is there any help for me and my informix server ???

> I have a performance problem with Informix IDS 7.30 UC5 on a SUN Solaris
> 5.5.1 (one processor with 512 MByte RAM)

> There is a table with 14 columns and 1.600.000 Rows.

> My Sql-Select is :

> SELECT lager, art_nr, SUM(menge)
> FROM lag_bew
> WHERE art_nr > 99000000
> GROUP BY lager, art_nr
> HAVING SUM(menge) > 10000
> ORDER BY art_nr

> The result contains 27 rows and takes 45 seconds ;-(.

> The same select on an NT-Server (smaller than the SUN) with Mr. Gates's
> Access takes only 25
> seconds (Thats true !).

> Informix does a sequential scan on the table an needs a temporary file for
> group and order by.
> The table has only 2 extents.

> If i create a index such as (art_nr, lager) or  (lager, art_nr)  the select
> takes over one minute (Thats true also !).
> The explain shows that Informix use this index and need no temporary file.

> The database has no transactions, the lock mode of the table is page and if
> i lock the table in exclusive mode the select is only 2 seconds faster.

> Now to the server:

> I'm using two cooked files, one for the rootdbs and one for the datadbs on
> the same disc-device.
> Does the performance increase so much if I'm using raw devices ?

> Here is my $ONCONFIG-File:



Wed, 18 Jun 1902 08:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Informix CLI 2.0 : problem with ODBC driver using MS-ACCESS and MS-QUERY

2. Informix CLI 2.0 : problem with ODBC driver using MS-ACCESS and MS-QUERY

3. INFORMIX ODBC 3.34 / MS-ACCESS / INFORMIX SE ( Solaris 7 )

4. ODBC Informix db access using MS Access

5. MS SQL Server work slower that Access 2.0?

6. MS Access 97 SR-1, psqlodbc 7.01.00.06, slow perfomance

7. MS Access 97 SR-1, psqlodbc 7.01.00.06, slow

8. ODBC 3.5 may slow down the VB4 or VB5 to access MS SQL6.5

9. Oracle slower than MS Access?

10. JDBC -> MS Access Slow Connection

11. Slow JDBC-ODBC to MS-Access DB


 
Powered by phpBB® Forum Software