Archives of the TeradataForum

Message Posted: Sun, 29 Jun 2003 @ 04:28:34 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi,

Ferret Defrag command works within a Cylinder. This isn't a FULL disk defrag like Microsoft where it tries to move each file (table) to be co located on consecutive cylinders.

Unlike Other database where you define specific table spaces for each table or group of tables any of our tables can be located anywhere across the whole disk.

I agree with Carrie and the other post that the statement probably refers to the more data on the disk the more head movement and therefore more seek time and Rotational latenency.

The couterpoint however is the DBA doesn't have to spend their time allocating Table spaces for particular tables every time more data is added to a table or a new table is allocated as our database manages the one and only table space allocated to the amp.

Also if a particular Table space fills up on those other databases and it has to be grown to accomedate more data wouldn't that allocation come from some where else on the disk and therefore also incur those same seek time and Rotational latenency penalties?

Or does everyone always know ahead of time how to allocate perfectly sized tablespaces on those other databases?

	<Prev	Next>		<<First	<Prev	Next>	Last>>