Hallo zusammen,wie von einer Weile

Hallo zusammen,

wie von einer Weile im MW-StandUp erwähnt besteht nun die Möglichkeit sich mit der Datenbank direkt über einen ReadOnly-User zu verbinden. Ein ensprechender User ist für die I-, K- und für die P-Umgebung eingerichtet.

Ich bitte Euch für Datenbankrechercheren primär diesen ReadOnly-User zu benutzen, weil:

für Euch die Sicherheit besteht, dass keine Änderungen am Datenbestand mit diesem User-Login möglich ist,
pro Umgebung nur noch ein Login notwendig ist, da zum Beispiel mittels dem ReadOnly-User für K sowohl Daten aus K1-ECOM, K2-ECOM, K4-ECOM, K1-TALEND_MD, K2_TALEND_MD und K4_TALEND_MD abgefragt werden können,
die verwendeten Ressourcen für die ReadOnly-User begrenzt werden können (so dass zum Beispiel kein ungünstiger SELECT die Datenbank lahm legen kann).

Im Unterschied zur bisherigen Datenabfrage im SQL-Developer erfolgt die Abfrage für den ReadOnly-User wie folgt:

Results (English) 1:

Hello together,as mentioned by a while in the MW StandUp now has the ability to connect to the database directly via a ReadOnly-user. Lakeshores user is set up for the I, k and P environment.I am asking you for Datenbankrechercheren to use this ReadOnly users, primarily because: for you, the security is that no changes to the database with this user login is possible per environment only a login is necessary, as for example using the ReadOnly-user for K both data from K1-ECOM, K2-ECOM, K4-ECOM, K1-TALEND_MD, K2_TALEND_MD and K4_TALEND_MD can be queried. the resources for the ReadOnly-user limited can be (so that for example no less favourable SELECT can cripple the database).In contrast to the previous data query in the SQL Developer, the query for the ReadOnly users is as follows:

Results (English) 2:

Hi,

as mentioned by a while in MW StandUp it is now possible to connect to the database directly from a read-only users. As an appropriate user is set for the I, K and the P-area.

I ask you for Datenbankrechercheren primarily use this ReadOnly users because:

the security is for you that no changes to the data with this user login is possible
per surroundings only one login is necessary because, for example, by means of the read-only user for K both data from K1-ECOM, K2-ECOM, K4-ECOM, K1 TALEND_MD, K2_TALEND_MD and K4_TALEND_MD can be queried,
the used may be limited resources for the ReadOnly users (so that, for example, no adverse SELECT can create the database lame).

in contrast to previous data requests in SQL Developer, the query for the ReadOnly users is as follows:

Results (English) 3:

hello, everybody,as a while, mw standup mentioned the possibility now exists with the database directly through a readonly users connect. a ensprechender user for the i, k and p for the environment set up.i beg you for datenbankrechercheren primarily the readonly user to use because:you are safe, that no changes to the database with the user login is possibleper area just a login is required as, for example, by using the readonly user data for k and k1 ecom, k2 ecom, k4 ecom, k1 talend _ md, k2 and k4 _ talend _ md _ talend _ md can be retrieved.the resources used for the readonly - user will be limited, so that, for example, no adverse select shut down the database).in contrast to previous data in sql developer is the query for readonly users as follows: