Re: DB fixup after migration

From: WangKhar (Wangkhar_at_yahoo.com)
Date: 05/28/04

  • Next message: Ryan Columbus: "Re: Is there a way to stop SQL Server from recording its uptime in the registry?" 
    Date: 28 May 2004 08:45:24 -0700

    So presumably after you complete your testing, then go through and
    rename all the references to dbs, then release, you are in effect
    releasing untested code?

    Nice.
    Thought I had problems...

    d_lwl@hotmail.com (David L) wrote in message news:<40ea64bd.0405130010.2e5e3266@posting.google.com>...
    > 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.
    > >
    > >...

  • Next message: Ryan Columbus: "Re: Is there a way to stop SQL Server from recording its uptime in the registry?"

    Relevant Pages

    • Re: Losing functionality after compiling to mde with MS Acess 2003
      ... could be that you have some references in you database, which are not present on "another environment". ... Check all your references and make sure that any not-built-in, office), present there. ... I have a database which is splitted in a front- and a backend. ... However I have tested the mde on my own pc and everything works fine. ...
      (microsoft.public.access.conversion)
    • Re: Losing functionality after compiling to mde with MS Acess 2003
      ... Check all your references and make sure ... I have a database which is splitted in a front- and a backend. ... However I have tested the mde on my own pc and everything works fine. ... However when I use the same mde on another environment I lose ...
      (microsoft.public.access.conversion)
    • Re: VB version difference
      ... I'm guessing that there's a problem with the References collection, ... If any of the selected references have "MISSING:" in front of them, unselect ... new database in the client's environment and importing all in. ...
      (microsoft.public.access.modulesdaovba)
    • Re: DB Architecture Questions (for joe celko)
      ... So a deck of punch cards or a mag tape is just like an SQL Schema to ... a table has a name in the database. ... OCCURS clause. ... This rule would be enforce by a REFERENCES clause on the Orders table ...
      (microsoft.public.sqlserver.programming)
    • Re: Table Design Question
      ... > requires more than two probes, no matter how large the database. ... > acceptable (in the relational model) to have an Identity attribute to ... the gap in the sequence is not filled in and the sequence ... > vin CHARNOT NULL REFERENCES Motorpool); ...
      (microsoft.public.sqlserver.programming)
    Loading