home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!gatech!usenet.ins.cwru.edu!agate!agate!robm
- From: robm@ishtar.Berkeley.EDU (Rob McNicholas)
- Newsgroups: comp.databases.ingres
- Subject: DB admin tools
- Date: 22 Dec 92 12:03:35
- Organization: Technical and Computing Services, U.C. Berkeley, Berkeley, CA
- Lines: 32
- Distribution: world
- Message-ID: <ROBM.92Dec22120335@ishtar.Berkeley.EDU>
- NNTP-Posting-Host: ishtar.berkeley.edu
-
- Hi all,
-
- I'm working on a database which is in a constant state of flux.
- Necessity dictated that we put it into production before we had really
- worked out all the problems, so I often find myself dropping and
- recreating tables to add a new field, or change a field's size or
- type, etc. After doing this once or twice, I quickly learned that
- there are many side effects of these kinds of changes. For example,
- dropping a table causes any views, forms, or permits which referred to
- that table to be destroyed also, so the DBA needs to create scripts to
- recreate all the different pieces, and remember to update these
- scripts whenever a change is made anywhere. Unfortunately, Ingres
- doesn't seem to provide any tools to help make this kind of change
- easier. I've been using unloaddb and then editing the scripts to
- recreate just the parts i need, but this is tedious, and it doesn't
- handle forms or views very well.
-
- I've been thinking about writing my own tools that would access the
- system catalogs and help find all references to a particular table or
- field, so that these changes would be easier to manage. But before I
- do it myself, I ask:
-
- Does anyone have any suggestions for any Public Domain or commercial
- products which would provide this kind of functionality?
-
- Thanks in advance,
-
- -Rob
-
- --
- Rob McNicholas Technical & Computing Services, EECS, U.C. Berkeley
- robm@eecs.berkeley.edu Voice: 510/642-8633 FAX: 510/643-7846
-