> > >Question 2: If not, what would the Insert/Select statement look like
> > would copy the records over in sorted order?
> > Tables aren't sorted. Period.
> > Only result-sets can be sorted.
> While that is true, strictly speaking, packing data into the same
> physical order as you expect to logically access it is a fairly common
> optimization for data which remains fairly static. Having said that,
> for the 1600 records reffered to here, I doubt there would be any
> observable difference.
As with what Dan said, this is _only_ useful if you can get the engine
to fetch the data in storage order. If not, there's no point.
And when do you actually get this data in "storage order"? Probably
only when doing a fetch on this single table from beginning to end.
And as both of you said: 1600 rows? What's the hassle.
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Database development questions? Check the forum!