Re: can you take a schema offline?
From: Palooka <nobody_at_nowhere.com>
Date: Fri, 13 Mar 2009 02:57:19 +0000
Message-ID: <iYjul.97054$ot7.42333_at_newsfe15.ams2>
Ed Prochak wrote:
>> On Mar 12, 1:54 pm, ddf <orat..._at_msn.com> wrote:
>>
>>> Have you considered locking the user accounts and expiring the
>>> passwords? This wouldn't affect other users who may have access to
>>> those tables/views/etc but it would prevent any applications or
>>> individuals from connecting to the database with those accounts.
>> I did consider that, but then the reason i wanted to make the schema
>> inaccessible was to see if anyone would complain after i did so. We use
>> (d) this schema as part of an application we did, so everyone else
>> reads/writes from/to its objects. Then the application was modified
>> and a second schema was created and all the tables and objects were
>> (presumably) transferred to the new schema. So the theory is, i should
>> be able to drop the old schema and nobody should scream at me.
>>
>>> Presuming no one 'screams' afterwards you could then drop the users.
>> This is what i'm hoping to avoid.
>>
>> If there's no way to do this, and if there is no such creature as an
>> "alter schema x offline" statement, then i'll just try dropping the
>> user.
>>
>> thank you.
>
> After you do a back up, right?
Date: Fri, 13 Mar 2009 02:57:19 +0000
Message-ID: <iYjul.97054$ot7.42333_at_newsfe15.ams2>
Ed Prochak wrote:
> On Mar 12, 5:39 pm, rgvguplb <rgvgu..._at_gmail.com> wrote:
>> On Mar 12, 1:54 pm, ddf <orat..._at_msn.com> wrote:
>>
>>> Have you considered locking the user accounts and expiring the
>>> passwords? This wouldn't affect other users who may have access to
>>> those tables/views/etc but it would prevent any applications or
>>> individuals from connecting to the database with those accounts.
>> I did consider that, but then the reason i wanted to make the schema
>> inaccessible was to see if anyone would complain after i did so. We use
>> (d) this schema as part of an application we did, so everyone else
>> reads/writes from/to its objects. Then the application was modified
>> and a second schema was created and all the tables and objects were
>> (presumably) transferred to the new schema. So the theory is, i should
>> be able to drop the old schema and nobody should scream at me.
>>
>>> Presuming no one 'screams' afterwards you could then drop the users.
>> This is what i'm hoping to avoid.
>>
>> If there's no way to do this, and if there is no such creature as an
>> "alter schema x offline" statement, then i'll just try dropping the
>> user.
>>
>> thank you.
>
> After you do a back up, right?
They don't document, audit nor follow any kind of change control procedure.
So why should they bother backing up either?
Palooka Received on Thu Mar 12 2009 - 21:57:19 CDT