Hi all. I've seen questions relating to this but not quite exactly the same as I'm looking for.
I realise there are no enforcements in terms of what to name tables, but was wondering what other peoples approaches are.
Lets say we have a development environment where multiple apps are being created. These model driven apps are called App1, App2 and App3 (obviously wouldn't be in real life but for the sake of this question).
If a table is specific to one app and not used by any others, do you prefix (or any other description) the table with the name of the app it is used by, so you know it relates to that app? E.g. App1_Vacancy. Or do you just call it Vacancy? A problem with adding the prefix, is that it displays the name of the table on a form, so it looks messy if you've added a prefix (it would show App1_Vacancy rather the just Vacancy on screen).
My feeling is that if we do the latter (plain name) it might get confusing as time goes on as to what it used by what.
Furthermore, what if two apps need a table that is very similar but with some differences? For example, if two apps need a People table, but some of the fields/columns will be different, do you create a different table in each solution such as App1_People and App2_People to differentiate?
There is also the whole publisher aspect as well, so do people create a new publisher for each app instead?
