Increase Database Name Length Restriction

Real Life Scenario:

With Devops and the introduction of "Infrastructure as Code", a database build can be done via Helm Charts, K8's, Cloudformation templates, etc. Automation can dramatically increase how often a database is built and how many clones that database may have. Because of this, a DBA has a need for a predetermined database naming convention. This naming convention can contain shorthand or abbreviations for environment type (i.e. Dev), project swim lanes (i.e. second copy of Dev for a new feature), build type (docker container vs. EC2), etc. These names can dictate what type of reporting, maintenance, development will hit that database.

Pain Point:

It is difficult to come up with a naming nomenclature with an 8 character database name limit. This is leading to extra coding on the management side (i.e. k8), documentation linking some numerical value to a project or devision, manual note taking, etc. Right now, SQL Server can have a 128 character limit, Oracle has a 30 character limit, mySQL has a 63 character limit. So when we try to come up with a naming convention that spans database types, we are limited to 8 characters. This may not be possible with z/OS, but should definitely be available for LUW especially if the DBA is pitching Db2 as an option for a microservice.

Users impacted:

In this specific scenario it takes at least two (DBA and system engineer) working together on each new database creation to come up with a feasible name and to maintain 1-2 extra documents manually. In a Devops shop with many database iterations this is a waste of time and resources.

Benefits/Value:

• This brings you more in line with your competitors

• This allows a naming convention that is more devops friendly

• This modernizes the database architecture.