Innodb stores it's indexes internally in the datafile; they do consume storage, but that space is shared with the data.
innodb_per_file will, in most cases, enhance performance in a high-concurrency environment. It also can simplify administration, and help limit your liabilities in the event of catastrophic filesystem error. - md On Tue, Oct 30, 2012 at 3:18 AM, Trimurthy <trimur...@tulassi.com> wrote: > hi lists 1. does the indexes require additional storage other than > the table space storage. 2. is there any performance difference > will be there, if we go for innodb_file_per_table. > > > > > > > Normal > 0 > > > > > false > false > false > > EN-US > X-NONE > AR-SA > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks & Kind Regards, > > TRIMURTHY > -- - michael dykman - mdyk...@gmail.com May the Source be with you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
