Morning, Hope everyone are still able to function after consuming all the turkey they can lay their eyes on I know I did ate a ton.

Here is a dilema that I am faced.

we have a group that refuse to use two part name for the tables. They are login in using id = ABC, tables are creatd under schema XXX. So, they are constantly getting table ABC.tab1 can't be found.

They demand that we create a bunch of aliases for them, which we are not going to do for varius reasons. It will create a housekeeping nightmare to begin with. Plus, they have that ability now to do it them selfs and we are not babysitters.

Now to force them to code properly and stop creating hundreds of aliases we have to disable their ability to create aliases them self. They obviusly don't need IMPLICIT_SCHEMA because they are creating them in their own schema. So, the only thing is left is to revoke CREATEIN abilitty.

Now, it apears to be a double sided sword. If we do that we will revoke their ability to create table, which I am not sure we can do because of their application needs.

Any recomendations on how to prevent them from creating alias beside a smack on a head

Thank you.

From the moment they cannot use aliases anymore, they will start using synonyms or views ...

Youa re saying that beating will continue until moral improves

Just a thought :
If you are using ODBC connectivity, you can include the CURRENTSCHEMA keyword in the db2cli.ini file
or
if using JDBC(eg. Webspher) you should be able to set the schema as a datasource property.

Cheers
Sathyaram

They have been told about those and some other choices back in April and they keep coming back.