cancel
Showing results for 
Search instead for 
Did you mean: 

Split database to client specific and cross client

Former Member
0 Kudos

Hi

Do we have a known method to split an existing MaxDB database into two .

1. Client Specific database

2. Cross client database

Thanks and Regards

Sri

Accepted Solutions (1)

Accepted Solutions (1)

TTK
Employee
Employee
0 Kudos

Hello

I'm not sure, what you want to do.

Shall the two resulting data bases be copies of the origin one?

Shall queries simultaneously go to both data bases and then be mixed together?

Shall the data (i.e. users, tables) be split into two different data bases?

Regards Thomas

Former Member
0 Kudos

Hi Thomas,

Thanks for your reply.

We would want the tables to be split into two different data bases depending on whether the table is client dependent or client independent. And the two databases should belong to the same system.

Regards

Srikishan

TTK
Employee
Employee
0 Kudos

Hello

In addition to Alexander's reply I would like to remark, that

- surely it is possible to handle two data base connections in one application

- data consistency might be really a problem, if the application is meant for changing data in both data bases.

- mixing the data between the data bases has to be done in the application.

What is your intention to split the data bases? Performance, network traffic, data size, scaling etc?

Regards Thomas

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Alex and Thomas,

Our intention was to seperate out the customer specifica and system specific data into two different DBs.

Thanks a lot for the clarification. I guess we need to think of something different to achieve the results.

Regards

Srikishan

markus_doehr2
Active Contributor
0 Kudos

What you can do is to use TDMS (Test Data Migration Server), it´s a separate product and it enable you to setup test/training systems with a reduced amount of production data.

This system makes use of technologies to determine, whether a table is client depend and client independent.

Your problem is, that the client specific data NEEDS the cross client data, it relies on the customizing, that is cross client.

If your pupose is to e. g. extract some kind of data because parts of your company was sold or if you bought a new company, then you should contact the SLO group (http://service.sap.com/slo) that does those kinds of "separations" too.

From a technical level, it´s certainly possible but wihtout knowing your initial intent why you want to do that, one can give just advises, what we "think" what the reason might be.

--

Markus

alexander_schroeder
Participant
0 Kudos

Hello Sri,

there is no way to 'split' a database as to selectively unload all tables that go into

such a partition using the loader tool, and import them into a database that is

newly created.

However, be aware, that you end up with two databases which are completely

independent, and must be handled at application level. (There is unfortunately

no way to access a table of another database in MaxDB in an SQL query, such as 'database links' known from other database management systems).

If your application is a R/3, there is currently no way for doing such kind

of partitioning.

Regards

Alexander Schröder