Re: SQL Table rename problem

On 03-Nov-2014 18:32 -0600, John Smith wrote:

Unfortunately, the desired result is to have both names.
We (the RPG developers) want to have a consistent naming such as
STGSTORE, STGWHSE, and STGITMMST (no underscores) but they (the SQL
developers) want to have STG_IN_STORE, STG_IN_WH, and
STG_IN_ITEM_MASTER.

It sounds like I need to convince them to change their table names to
be > 10 characters <<SNIP>>

Yeah, having two valid system-names for a file is not going to happen; just as the message text for the msg SQL7029 should suggest.

The SQL folks will want [hopefully are amenable] to choose names that are valid only as an Alternative file name [aka long file name]. From the names above, the more obvious choice for the name corresponding to STGWHSE would be [rather than the disallowed value "STG_IN_WH"; not sure why they would have settled on using the WH abbreviation anyhow, when comparing that name with the other examples] one of:
STG_IN_WHSE or STG_IN_WAREHOUSE

FWiW: As alluded in my prior reply, the excessive length is not the only criteria allowing for a valid alternative name. Names that must be delimited due to characters not supported in a valid delimited system-name can be a /short/ alternative file name [thus why the term /long file name/, although often used to describe the alternative name, is a misnomer]; e.g. the valid SQL name "STG*IN" is not a valid delimited system-name, so can only be an alternative file name, yet even with the delimiters is still less than 10 characters. Of course names with embedded blanks or most special characters are discouraged anyhow.