|
Home > Archive > SQL Anywhere Feedback > July 2005 > allow Disable_Connections to be set for an individual database
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
allow Disable_Connections to be set for an individual database
|
|
| Justin Willey 2005-07-08, 7:23 am |
| It would be useful to have a simple method to prevent connections to a
single database running on a server while maintenance procedures are carried
out.
This can be achieved by modifying the login procedure, but this is difficult
when one is trying to automate an update across many client sites, where the
login procedure may have been modified from the default. Barring access to
all databases on the server can cause problems whre users have other
production databases.
Justin Willey
| |
| Breck Carter [TeamSybase] 2005-07-08, 9:23 am |
| What do you think of this suggestion?...
=====
Newsgroups: sybase.public.sqlanywhere. product_futures_disc
ussion
Subject: Disable groups of user ids
Date: 31 May 2005 14:05:44 -0700
=====
In spite of Glenn's response to that posting, I *still* want it...
well, the client wants it... enabling a database is a staged process
for them, allowing some kinds of connections but not others, over a
period of minutes or hours as proper operations are verified. Rolling
back an upgrade is easier during the early stages, gets harder as more
classes of users are permitted. Free-range users come last :)
Breck
On 8 Jul 2005 05:10:36 -0700, "Justin Willey"
<gjw@nospamatall.iqx.co.uk> wrote:
>It would be useful to have a simple method to prevent connections to a
>single database running on a server while maintenance procedures are carried
>out.
>
>This can be achieved by modifying the login procedure, but this is difficult
>when one is trying to automate an update across many client sites, where the
>login procedure may have been modified from the default. Barring access to
>all databases on the server can cause problems whre users have other
>production databases.
>
>Justin Willey
>
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Justin Willey 2005-07-13, 9:23 am |
| I can see the attraction. It wouldn't help in our particular case though, as
all users log in under a single ID and we manage user rights (including
automated database maintenance / updating) at an application level.
Justin
"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:a6usc11c01notoo
mqdm3k0rav55iarqq9v@
4ax.com...
> What do you think of this suggestion?...
>
> =====
> Newsgroups: sybase.public.sqlanywhere. product_futures_disc
ussion
> Subject: Disable groups of user ids
> Date: 31 May 2005 14:05:44 -0700
> =====
>
> In spite of Glenn's response to that posting, I *still* want it...
> well, the client wants it... enabling a database is a staged process
> for them, allowing some kinds of connections but not others, over a
> period of minutes or hours as proper operations are verified. Rolling
> back an upgrade is easier during the early stages, gets harder as more
> classes of users are permitted. Free-range users come last :)
>
> Breck
>
> On 8 Jul 2005 05:10:36 -0700, "Justin Willey"
> <gjw@nospamatall.iqx.co.uk> wrote:
>
carried[color=darkre
d]
difficult[color=dark
red]
the[color=darkred]
to[color=darkred]
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
http://www.amazon.com/exec/obidos/A...7/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com
| |
| Martin Baur 2005-07-13, 8:23 pm |
| In article <42ce6d39@forums-2-dub>, gjw@nospamatall.iqx.co.uk says...
> It would be useful to have a simple method to prevent connections to a
> single database running on a server while maintenance procedures are carried
> out.
I support this and propose to have a new privilege like in Oracle. In its "mounted" stage, onlce users/groups having a special privilege can connect.
Even it there is no such thing as a "mounted" stage, a privilege/right can be easily assigned/removed. Removal of this right should have a side-effect that users are logged-out gracefully (whatever
this means).
--
Martin Baur
MindPower.com, IT-Services
|
|
|
|
|