Thanks for the offer but purchasing software is not in the path of the
barge.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Karl
Haggart
Sent: Tuesday, February 15, 2022 12:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Question for migrations of SQL source / objects
Hi,
From a vendor perspective, all change management solutions will handle this
for you.
If you would like to see how Remain's product, TD/OMS, would do so quickly
and in a cost effective manner, I would be happy to share more details and
show you how things would work in your particular scenario.
Thanks,
Karl
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
smith5646midrange@xxxxxxxxx
Sent: Tuesday, February 15, 2022 9:06 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Question for migrations of SQL source / objects
We have stumbled over a problem and I am curious how it is normally handled.
The libraries in our environments have different names based on the
environment. For example, the libraries for dev testing might be DATADEV1,
DATADEV2, etc. while the library for user testing might be DATAUSR1,
DATAUSR2, etc.
When there is source to create stored procedures, views, etc., how do
companies deal with the varying library names when they need to be included
in the definition because they are not part of the normal library list?
I'm also curious about how packages like Turnover, Aldon, etc. handle this
if anyone knows that.
I know there are better ways to handle this by "fixing" the environment
library lists and such but I can't turn the barge with an oar so the
environment is what it is and I have to work within the current parameters.
Thanks in advance for any insight you can provide.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
