Re: DB fixup after migration
From: David L (d_lwl_at_hotmail.com)
Date: 05/13/04
- Previous message: Silas: "Select Record with Chinese Return None"
- Next in thread: WangKhar: "Re: DB fixup after migration"
- Reply: WangKhar: "Re: DB fixup after migration"
- Messages sorted by: [ date ] [ thread ]
Date: 13 May 2004 01:10:54 -0700
our convention (I am powerless to change it) calls for adding a suffix
to the database name. The suffix (_SD, _SU , _SP etc) relates to the
environment where this database normally operates (development, user,
production). Problem occurs when some of the views and/or stored
procedures started to refer to objects in a different database. And
later on the entire database is copied to another environment.
After the copy, the interdatbase references are wrong in the new
environment.
DavidQR
13 May
"Greg D. Moore \(Strider\)" <mooregr_deleteth1s@greenms.com> wrote in message news:<Kn_jc.126565$e17.78317@twister.nyroc.rr.com>...
> "David L" <d_lwl@hotmail.com> wrote in message
> news:40ea64bd.0404272105.592c9469@posting.google.com...
> > We have a recurring problem due to the use of a naming convention
> > where database names are suffixed by the environment (e.g. SD for
> > development).
> >
> > The result is that after a database copy from production to
> > development, all references to objects in a different database would
> > have the wrong qualifier.
>
> I'm not 100% sure what exactly the problem is here.
>
> In dev you call a database SD_FOO but in production you call it FOO?
>
> Not really seeing the point, why not name the same in both environments.
>
>...
- Previous message: Silas: "Select Record with Chinese Return None"
- Next in thread: WangKhar: "Re: DB fixup after migration"
- Reply: WangKhar: "Re: DB fixup after migration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
