There's not enough information here to give you a good suggestion for your case, particularly in terms of dimension record count. Here are some guidelines.
If you absolutely need it there as a business requirement, then you need it. Usually in the dimensions this is not an issue, unless it is a degenerate dimension. If the dimension has about the same number of rows as the fact table, it is probably degenerate.
Street addresses in the fact table are not automatically bad, but they are usually not good. If the fact table is millions of records, the presense of these long fields makes everything slower. Whether it is too slow is up to you and your users. Ideally the fact table consists of pointers to dimensions so that the rows are as small as possible. As long as the trade-off is understood, then do it. I personally prefer my operational reports requiring that detail to come from the operational database.