Re: test and production on same database ??

Catherine,

It's fine to create these tables in different schemas and control access as suggested but in all honesty it is best to keep production and testing apart in different databases preferably on different servers (although this isn't always achieveable due to hardware constraints).

Reason being, testing is intended to address the functionality of the system and to monitor how it performs under test circumstances. These test circumstances should mirror the production environment as closely as possible. This cannot be realistically achieved if the database is also being used in parallel as a production site. You could/probably would get conflicting results from testing especially in the area of performance. Testing could also have a detrimental effect on users of the production data also which must be considered.

In my experience, splitting the two databases is the safest course of action.

Catherine VOGEL wrote in message <85k6fd$1nn$1_at_news.mgn.net>...
>Hello
>
>Here is french asking !
>
>How can we do for having on same database one access on data of users and
>another access on data for tests ?
>
>congratulation for attentive responses
>
>best regards
>
>Jean-François Burgos
>A++
>
>
>
Received on Thu Jan 13 2000 - 05:50:08 CST