Hi
It sounds like you are running multiple test and production schemas in a
single database, which to me seems quite a dangerous thing to do, not only
that the administration is made much difficult but because you have to make
changes to scripts and code between test and live. Having a separate
database with the same schema would mean that once tested the same code can
be used on the live database.
You should also look at maintaining code in version control which you
probably are not doing.
Loading the scripts using osql/isql and command files will mean that you can
use dos scripts to provide substitution variables for databases.
John
"Patrick" <pa*********@statcan.ca> wrote in message
news:63**************************@posting.google.c om...
Hi,
The company's database has multiple schema.
If I want to modify a stored procedure, which is saved as a script
(something like abc.sql), I opened that script in Query Analyser, made
the changes, tested in Development Schema and saved it. After that, if
I want to make those changes to other schemas, of course I can select
different schemas and run the script. If there are many many schema,
there is a likelihood that we miss one schema.
So, I just want to know whether I can write a script, which accepts a
list of schema names, (e.g. 'schema1, schema2, schema3,...', and
script name (like abc.sql), then I can update all schema in one shoot.
Thanks
Patrick
