RE: Renaming SQL Database? -- MIDRANGE-L

Subject: RE: Renaming SQL Database?
From: Rob Berendt <rob@xxxxxxxxx>
Date: Mon, 9 Mar 2020 13:03:25 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

See
WRKRDBDIRE
If you're really good you can set up an alias to cover both the old name and the new name. I do it for H/A systems.
Remote
Entry Location

GDISYS GDISYS1
GDISYS1 *LOCAL

I have a GDISYS1 machine and a GDISYS2 machine. At all times one or the other is acting as GDISYS.

This is the GDISYS alias on GDISYS1:

Relational database . . . . . . : GDISYS1
Relational database alias . . : GDISYS
Remote location:
Remote location . . . . . . . : GDISYS1
Type . . . . . . . . . . . . : *IP

Note: BRMS should use the GDISYS1 name and not the GDISYS name.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.