I am working with a customer who will have 1000's of clients. Currently we are planning to move to a 'multi-tenant' database whereas groups of 100 customers will be within a single database with all the ID's and such to discern by customers.

Until we get there I am trying to get input from others on naming conventions they may of used in the past for single databases where we can have 100's until we get to multi-tenant.

I was thinking to name releated to State and CustomerID something like
db_TX_100019 ?

As I am not expert on MySQL was wondering what others may think, in the long run what would be the best method for naming. I am thinking about the fact that we may take a year or more to get the multi-tenant complete and was thinking about support and such.

Basically trying to find out the 'best' way from others that may of done this in the past.

Thanks for reading

From The Dark Side Of The Moon!

Short answer: don't use multiple databases. Use a single database.

Why would you want to split the data up in such a way when you could write queries to show such results instead?

George, he doesn't want to.
They're moving to a multi-client db design. He just needs an interim solution.

Mr. Floyd, your naming convention should suffice, except that you should drop the "db_" prefix. Prefixing database objects with their object type ("tbl" for tables, "vw" for views, etc) is a relic of procedural programming.
"db_" supplies no information. Obviously, its a database.
Instead, prefix with the name of the application:
OurBloatedApp_TX_100019
I'd also suggest padding the customer number with leading zeros as necessary so that the customer number lengths are all identical. This will make them sort consistently.

Thanks for the input. As we have other 'databases' on these servers the db_ prefix would allow sorting by the customers.

Appreciate the input and thanks to all that read and replied.

I don't get

Where is the data now?

Where is the data going to go to?

Uhmm...NO. Adding "db_" to all the database names does not affecting sorting, as they all have the same prefix. And as I pointed out, "db_" contains not informational value. Use the application name instead of "db_".
Using "db_", or even worse "tbl_" is just noobish.

i see people using "tbl_" prefix on table names all the time, and not a single one of those people admits to also using the "col_" prefix on columns

only once has anyone ever even responded to my suggestion to use "col_", and it was to say "no, that'd be silly" to which i gleefully replied "my point exactly!"