Re: SE: Can't drop transaction logging

->From: spitz@GANS1X.ana.med.uni-muenchen.de (Richard Spitz) ->Subject: SE: Can't drop transaction logging ->Date: Wed, 13 Apr 1994 11:52:38 GMT ->Reply-To: spitz@ana.med.uni-muenchen.de ->Organization: Institut fuer Anaesthesiologie der Universitaet Muenchen -> ->In a SE 4.1 database, I just discovered that the person who created ->it used only a relative pathname for the transaction log file. This ->makes it impossible to access the database from other directories. -> ->I wanted to change that following the description in the 4.0 SQL manual. ->I logged in as the DBA for that database and tried to issue the ->following SQL command: -> ->DELETE FROM systables WHERE tabname = "syslog" -> ->This produces an error "No delete privilege". -> ->What's going on here? Is there a possibility how I can drop transaction ->logging on this NON-ANSI SE database in 4.1? -> ->Regards, Richard Richard, Two possible solutions, at least partial ones: 1. Can you update systables.dirpath to contain an absolute path for syslog? This won't drop logging, but will let you run from other directories. 2. Can you change systables.tabtype to be blank instead of 'L' for syslog. I'm less certain about this approach, but I seem to remember that this is a way to turn off the logging. I have successfully made changes like the first, but have never tried the second, only read about it. Regards, Alan ___________________________ ______________________| R. Alan Popiel |__________________________ \\ Internet: | Martin Marietta, SLS | / \\ alan@den.mmc.com | P.O. Box 179, M/S 3810 | Std disclaimers apply. / )Voice: | Denver, CO 80201-0179 USA | ( / 303-977-9998 |___________________________| (But you knew that!) \\ /________________________) (____________________________\\