[rt-users] RT2 Database design...

[Simon Woodward]

I realise this deviates from the question a little, but while we are
talking about database design, what about the addition of several
customisable fields in the database which could be included to reference
each ticket by ...

I'm thinking about the possibility for organisations to add customer or
account numbers that coincide with their own internal databases which
could then be searched on and keyed as well as by email address.

Although going back to your question, It looks to me like the
attachments table has one primary key, that of id and one key of
transaction id I think the more indexing the better, and the more things
that are searchable (as far as the RT interface is concerned) the
better. But indexing will (afaik, please correct me if I am wrong here,
I'm not a DBA ;-)) only improve speed if the fields are the ones being
searched in the select query, so if the searching is only using the id
and TransactionId fields then I cant see what else could be done here. 

Simon.