RE: storing table on disk

I think a safe way might be to dump the specific tables, create the log file group, tablespace, and then edit the SQL statement to use STORAGE DISK and import the table into the tablespace.

I've read the MySQL manual as well, but there doesn't seem to be any guidelines as to how to determine what sizes should be used for the undo log files' INITIAL_SIZE or the size for the UNDO_BUFFER_SIZE or INITIAL_SIZE for the data files. Does anyone have any information regarding how to determine optimal values for these sizes?

-Bond

> -----Original Message-----
> From: B. Keith Murphy [mailto:kmurphy@icontact.com]
> Sent: Monday, October 08, 2007 1:24 PM
> To: cluster
> Subject: storing table on disk
>
> I am interested in converting some cluster tables to store
> the non-indexed columns on disk. I have a cluster up and
> running on the 5.1.20 version of mysql cluster. All tables
> are currently stored in memory. I want to convert some of
> them to be on-disk.
>
> There is a nice document here:
> http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-disk-data
-objects.html
>
> but it doesn't talk about converting a current in-memory
> table to on disk. Any help appreciated!!
>
> Thanks,
>
> Keith
>
> --
> B. Keith Murphy
> Database Administrator
> iContact
> 2635 Meridian Parkway, 2nd Floor
> Durham, North Carolina 27713
> blog: http://blog.paragon-cs.com
> (o) 919-433-0786
> (c) 850-637-3877
>

-- 
MySQL Cluster Mailing List
For list archives: 
http://lists.mysql.com/cluster
To unsubscribe:    
http://lists.mysql.com/cluster?unsub=lists@pantek.com