Free form text in transaction table

If a transaction has a free form text field as a description which has 1:1 correspondence with its facts, how do you model it. Are there any disadvantages to making it part of the fact table ?

Thanks

You don't want to put a text field in a fact table. It will significantly impact query performance.

Also, the reality is, this is not 1:1 as more often than not, the field is blank and there is a tendancy for people to use the same comment for similar situations. The best approach is to use a generic text dimension. This is discussed in http://forum.kimballgroup.com/dimensional-modeling-and-data-architecture-f6/booking-number-and-description-in-the-fact-table-t405.htm

Thats brilliant. Thanks ngalemmo.