All the User and System Data Sources defined in the registry are listed alphabetically.

Firefox Tip: If you have the Firefox "Remember Passwords" feature turned on (Tools - Options - Privacy - Saved Passwords), you may want to respond "Never for this site" when Firefox asks "Do you want Password Manager to remember this logon?" Otherwise, an old password may remain in the Password field when you switch between different databases. To clear a saved password from Firefox, use Tools - Options - Privacy - Passwords - View Saved Passwords - Remove.

ODBC Tip: Performance may be very bad for a database that isn't already running and has both of the following checked in the ODBC Administrator - Database tab:

• Start database automatically
  
  
• Stop database after last disconnect
  
  

The workaround is to un-check Stop database after last disconnect, so the database doesn't stop and start each time you display a different table.

The link will then change to Only show SQL Anywhere DSNs to indicate that if you click on it again, the Choose a DSN: list change back to including only those DSNs where the driver names starts with "Adaptive Server Anywhere" or "Sybase SQL Anywhere".

The engine is implemented as a SQL Anywhere 9 personal server, together with a small local database; it does not appear as an icon in the system tray or task bar. Your can also use the $stop_foxhound_engine.bat file to stop the engine.

Tip: It's OK to leave the Foxhound engine running all the time, it's got a small footprint. Or you can stop it if you need the RAM; it will be started again the next time you run one of the $start_*.bat files.

The table letter list C D E F ... can also be used to scroll the left frame down to individual starting letters in the table name list.

The column letter list A B C D ... can also be used to scroll the left frame down to individual starting letters in the column name list.

Foxhound issues a CHECKPOINT command to the target database so that it will bring the system tables up to date; in particular, it will update the column counts. It then refreshes the current display to show the up to date information.

The row counts are up-to-date as of the last CHECKPOINT done on the target database.

The space used includes table, extension and index pages including keys.

Bytes per row can be used to extrapolate disk requirements. It is calculated as the total disk space used for table, extension and index pages including keys, divided by the number of rows. It is only shown for tables that have more than 1 table page, and/or more than 1 extension page. It is not shown for smaller tables because it's usually not meaningful; i.e., a table with 1 ten-byte row in a 4K page would show as having 4,096 bytes per row.

For more information about disk space usage in SQL Anywhere, see Chapter 10 Tuning in the SQL Anywhere Studio 9 Developer's Guide.

• PK - this column is part of the PRIMARY KEY constraint defined later in the CREATE TABLE statement.
  
  
• FK - this column is part of one or more FOREIGN KEY constraints defined later as ALTER TABLE statement(s).
  
  
• U - this column is part of one or more unique indexes, defined later as either UNIQUE constraint(s) or CREATE INDEX statement(s).
  
  
• X - this column is part of one or more non-unique indexes defined later as CREATE INDEX statement(s).
  
  

This information is up-to-date as of the last CHECKPOINT done on the target database.

The total space for each table is shown in Kilobytes, Megabytes or Gigabytes. This number is broken down into table page space, extension page space and index page space; e.g.: 2.5G total = 2.2G table + 83.8M ext + 236M index

The index page space is also shown separately for each primary key, foreign key, unique constraint and index.

Bytes per row can be used to extrapolate disk requirements. It is calculated as the total disk space used for table, extension and index pages including keys, divided by the number of rows. It is only shown for tables that have more than 1 table page, and/or more than 1 extension page. It is not shown for smaller tables because it's usually not meaningful; i.e., a table with 1 ten-byte row in a 4K page would show as having 4,096 bytes per row.

For more information about disk space usage in SQL Anywhere, see Chapter 10 Tuning in the SQL Anywhere Studio 9 Developer's Guide.

• No foreign keys
  
  
• No transaction log (dbinit -n)
  
  
• No mirror log (no dbinit -m file)
  
  
• Blank padding for comparisons (dbinit -b)
  
  
• Case sensitive comparisons (dbinit -c)
  
  
• More views than base tables
  
  
• UNC file specifications are in use
  
  
• No clustered indexes
  
  
• No secondary indexes or unique constraints
  
  
• No explicit PCTFREE settings
  
  
• Database file version     a.b.c.d     -- different from engine version a.b.c.d
  
  
• More than one dbspace     nn     -- for tables and indexes
  
  
• Few tables with foreign keys     xx%     -- 25% or fewer
  
  
• Many file fragments     nn      -- 100 or more in database and temporary files
  
  
• Small maximum cache relative to database size     -ch nnK     -- nn% of nnK (10% or smaller)
  
  
• Database page size     nK     -- different from 4K
  
  
• Multiprogramming level     -gn nn     -- different from default 20
  
  
• Many NULL columns     nn%     -- 25% or more
  
  
• Column names with differing data types     nn     -- see "differs:" in Columns
  
  
• SET OPTION PUBLIC.xxx     = 'yyy'     -- different from default 'zzz'
  
  
• Largest tables ( xx% of the rows and yy% of the total space)...
  These tables are selected independently by row count and by total space used to include at least 80% of the rows and 80% of the total space.

• -- no primary key, unique constraint or unique index
  
  
• -- self-referencing foreign key relationship (fishhook)
  
  
• -- possibly invalid view (no column definitions in SYSCOLUMN)
  
  
• -- cascading foreign key action (CASCADE or SET)
  
  
• -- long columns (max length 100 or more) not all at end of row
  
  
• -- clustered primary key index
  
  
• -- clustered foreign key index
  
  
• -- clustered unique constraint index
  
  
• -- clustered secondary index
  
  
• nn     -- most bytes per row in a base table
  
  
• nnK     -- most total space in a base table
  
  
• nnK     -- most table space in a base table
  
  
• nnK     -- most extension space in a base table
  
  
• nnK     -- most index space in a base table
  
  
• nn     -- most columns in a base table
  
  
• nn     -- most indexes for a base table
  
  
• nn     -- most parent relationships
  
  
• nn     -- most child relationships
  
  
• nn     -- most columns in a proxy table
  
  
• nn     -- most columns in a global temporary table
  
  
• nn     -- most columns in a view
  
  
• nn     -- most columns in a materialized view
  
  
• nn     -- large number of bytes per row (500 or more)
  
  
• nn     -- large number of columns (50 or more)
  
  
• nn     -- large number of indexes (10 or more)
  
  
• nn     -- large number of secondary indexes (5 or more)
  
  
• nn     -- large number of columns in the primary key (5 or more)
  
  
• nn     -- large number of columns in a foreign key (5 or more)
  
  
• nn     -- large number of columns in a secondary index (5 or more)
  
  
• nn     -- large number of parent relationships (5 or more)
  
  
• nn     -- large number of child relationships (10 or more)
  
  
• nn%     -- large fraction of total rows (10% or more)
  
  
• nn%     -- large fraction of total space (10% or more)
  
  
• nn%     -- large fraction of total table space (10% or more)
  
  
• nn%     -- large fraction of total extension space (10% or more)
  
  
• nn%     -- large fraction of total index space (10% or more)
  
  
• db     -- different dbspace for table
  
  
• db     -- different dbspace for index
  
  
• nn%     -- most index space relative to table space
  
  
• nn%     -- large amount of index space relative to table space (80% or more)
  
  
• idx     -- duplicate [clustered] unique index - matches [clustered] primary key index
  
  
• idx     -- duplicate [clustered] unique constraint - matches [clustered] primary key index
  
  
• idx     -- duplicate [clustered] index - matches [clustered] primary key index
  
  
• idx     -- duplicate [clustered] unique index - matches [clustered] foreign key index
  
  
• idx     -- duplicate [clustered] unique constraint - matches [clustered] foreign key index
  
  
• idx     -- duplicate [clustered] index - matches [clustered] foreign key index
  
  
• idx     -- duplicate [clustered] unique index - matches [clustered] unique index
  
  
• idx     -- duplicate [clustered] unique constraint - matches [clustered] unique index
  
  
• idx     -- duplicate [clustered] index - matches [clustered] unique index
  
  
• idx     -- duplicate [clustered] unique index - matches [clustered] unique constraint
  
  
• idx     -- duplicate [clustered] unique constraint - matches [clustered] unique constraint
  
  
• idx     -- duplicate [clustered] index - matches [clustered] unique constraint
  
  
• idx     -- duplicate [clustered] unique index - matches [clustered] index
  
  
• idx     -- duplicate [clustered] unique constraint - matches [clustered] index
  
  
• idx     -- duplicate [clustered] index - matches [clustered] index
  
  
• nn     -- reserved words used as names (see "quotes" in table definition)
  
  
• nn%     -- small PCTFREE specified (10% or less)
  
  
• nn%     -- large PCTFREE specified (90% or more)
  
  
• col     -- UNIQUEIDENTIFIER primary key column