HANA eFashion Schemas for Training the team

[former_member203134]

Dear HANA friends,

Using the System user, we already created the 'efashion' project, starting with 'efashion_create_schema.sql.'

We are starting the training to the wider team, and idea is if the we create test users, say test1, test2... testn, and all get the "same" sql file.

Question is, will it create a new 'efashion' schema for every user, and thus a good idea for wholistic training (from schema creation to views, to reports) ? Or a one schema name in one database will prevail, so running the same schema creation sql will overwrite it, even if ran by different users?

Regards

Manish Madhav

[tomas-krojzl · Accepted solution]

Hello,

to fully separate users from each other you should adjust the tutorial to not use efashion schema but to use users schema. Each user should have it's own schema and it's own package. This way he can destroy only his work and not work of others.

If you keep the efashion schema then users will be overwriting the same schema again and again during import.

Alternative is to keep it as central schema for all users and grant users only read privileges and to show import operation on presenter screen only (users will not have opportunity to try themselves).

Tomas

[former_member203134 · Accepted solution]

Dear Tomas,

Can you please help elaborate a bit more.

By user's own schema you mean to something like the below?

CREATE SCHEMA efashion OWNED BY train1;

Will this suffice, or something more to care for? I belive the schema name can remain same in this case?

[tomas-krojzl · Accepted solution]

Hello,

actually this is covered by SAP HANA Pocketbook itself...

(I hope I do not have old version)

see on page 11 - 2.2 Create The E-Fashion Tables In the SAP In-memory Database

Modify the CREATE COLUMN TABLE statements according to your schema name. For example:
CREATE COLUMN TABLE <u201DSCHEMA_NAMEu201D>.u201CSHOP_FACTSu201D
could become
CREATE COLUMN TABLE u201DMY_EFASHIONu201D.u201CSHOP_FACTSu201D

see on page 17 - step 8. Save all views

there is attribute view on image with package "i826871-efashion"..

What you can do is to make rule that:

User: TRAININGNN

Schema: efashonNN

Package: efashionNN

Where NN is number of user. Every user then will need to always use HIS schema for tables and HIS package for views.

Tomas

[former_member203134 · Accepted solution]

Super cool answer! thanks.