Hi Carlos,

Thanks for the reply and for sticking with me on this issue! We had similar "fast" results earlier today when accessing a different table with very few fields but just as many (200K) rows. I seem to only be seeing or noticing this unacceptable time/execution delay behavior when the table is large (both in fields and records). But maybe, it has more to do with the existence of a particular field or data type, such as when large tables that contain a field defined as "TEXT" or something? Below is the MySQL script that builds the source table I am actually selecting against:

CREATE TABLE IF NOT EXISTS  testdb.mycfstble (
	cfs_index decimal(24,4) NOT NULL PRIMARY KEY,
	event_no char (12) NULL,
	incident_no char (12) NULL,
	agency char (6) NULL,
	call_type char (8) NULL,
	event_type char (1) NULL,
	priority int NULL,
	date_reported datetime NULL,
	time_reported char (8) NULL,
	call_source char (1) NULL,
	datetime_rpt datetime NULL,
	location_index decimal(24,4) NULL,
	location char (60) NULL,
	digits char (6) NULL,
	dir char (2) NULL,
	street char (30) NULL,
	st_type char (2) NULL,
	suffix char (2) NULL,
	apartment char (6) NULL,
	city char (20) NULL,
	county char (6) NULL,
	beat char (6) NULL,
	sector char (6) NULL,
	district char (6) NULL,
	latitude int NULL,
	longitude int NULL,
	description text NULL,
	rep_party char (40) NULL,
	rp_location char (40) NULL,
	rp_area char (3) NULL,
	rp_phone char (8) NULL,
	req_contact bit NULL DEFAULT 0,
	pri_unit char (6) NULL,
	sec_unit char (6) NULL,
	officer_id char (6) NULL,
	officer_id2 char (6) NULL,
	dispatcher char (6) NULL,
	time_disp datetime NULL,
	time_disp2 datetime NULL,
	time_enroute datetime NULL,
	time_enroute2 datetime NULL,
	time_arrive datetime NULL,
	time_arrive2 datetime NULL,
	time_clear datetime NULL,
	time_clear2 datetime NULL,
	total_consumed int NULL,
	emd_code char (6) NULL,
	disposition char (6) NULL,
	disp_cmnts text NULL,
	ent_oper char (6) NULL,
	date_enter datetime NULL,
	updt_oper char (6) NULL,
	date_updt datetime NULL,
	modify_flag bit NULL DEFAULT 1,
	rec_lock int NULL DEFAULT 0,
	timestamp_column timestamp (14) NULL,
	last_name char (20) NULL,
	first_name char (14) NULL,
	middle_name char (14) NULL,
	dob datetime NULL,
	mni_index decimal(24,4) NULL,
	invl_index decimal(24,4) NULL,
	press_release bit NULL DEFAULT 0,
	omit_from_view char (1) NULL,
  INDEX cfs_index (cfs_index),
  INDEX agency (agency),
  INDEX call_type (call_type),
  INDEX datetime_r (datetime_rpt),
  INDEX date_repor (date_reported),
  INDEX event_no (event_no),
  INDEX incident_n (incident_no),
  INDEX pri_unit (pri_unit),
  INDEX rec_lock (rec_lock),
  INDEX sec_unit (sec_unit));

In my production code that builds the view (this is the same production code that works perfectly in MS-SQL Server) I am defining most of the fields in the table but not all on my AS SELECT portion of the view definition. In my test code that I posted earler I used SELECT * for readability but the delays getting the view built seem the same in either case.

Alec