Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

What is the best way to keep users out of the database during a database update?

3 posts in General Discussion Last posting was on 2005-03-03 13:55:10.0Z
Lorraine Ford Posted on 2005-03-02 15:41:07.0Z
Reply-To: "Lorraine Ford" <lford@ttisoftware.com>
From: "Lorraine Ford" <lford@ttisoftware.com>
Newsgroups: ianywhere.public.general
Subject: What is the best way to keep users out of the database during a database update?
Lines: 20
Organization: Transportation Technologies Inc.
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4942.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
NNTP-Posting-Host: h-69-3-43-2.phlapafg.covad.net
X-Original-NNTP-Posting-Host: h-69-3-43-2.phlapafg.covad.net
Message-ID: <4225de93$1@forums-1-dub>
Date: 2 Mar 2005 07:41:07 -0800
X-Trace: forums-1-dub 1109778067 69.3.43.2 (2 Mar 2005 07:41:07 -0800)
X-Original-Trace: 2 Mar 2005 07:41:07 -0800, h-69-3-43-2.phlapafg.covad.net
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:4181
Article PK: 8059

We have many customers who do not enforce keeping their users out of the
database
while they are running our software updates at the databse server which also
update their database.
This causes tables to be locked and therefore they do not get updated properly.

We were wondering what other people are doing to ensure the database is
on stand alone mode when doing your updates:
These two things have been suggested to us:
1) temporarily change the dba password while doing the update so no one can
connect, then change it back after the update.
2) Use the dbconsole utility to block any additional connections then run our
update.

Has anyone had success doing either, or do you do something altogether
different?
Any ideas would be appreciated!
Thanks,
L.Ford


Breck Carter [TeamSybase] Posted on 2005-03-02 18:53:02.0Z
From: "Breck Carter [TeamSybase]" <NOSPAM__bcarter@risingroad.com>
Newsgroups: ianywhere.public.general
Subject: Re: What is the best way to keep users out of the database during a database update?
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__bcarter@risingroad.com
Message-ID: <jj2c21hjl0ns9c2v47h8o7utqoj5vmtdg0@4ax.com>
References: <4225de93$1@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: bcarter.sentex.ca
X-Original-NNTP-Posting-Host: bcarter.sentex.ca
Date: 2 Mar 2005 10:53:02 -0800
X-Trace: forums-1-dub 1109789582 64.7.134.118 (2 Mar 2005 10:53:02 -0800)
X-Original-Trace: 2 Mar 2005 10:53:02 -0800, bcarter.sentex.ca
Lines: 41
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:4186
Article PK: 8064

Do this Google Groups search...

p_drop_other_connections group:sybase.public.sqlanywhere.*

That procedure is also on
http://ianywhere.codexchange.sybase.com/servlets/ProjectDocumentList
... do a search on sa_drop_other_connections in the ASA section.

Instructions are contained inside the procedure, as comments.

Breck

On 2 Mar 2005 07:41:07 -0800, "Lorraine Ford" <lford@ttisoftware.com>

wrote:

>We have many customers who do not enforce keeping their users out of the
>database
>while they are running our software updates at the databse server which also
>update their database.
>This causes tables to be locked and therefore they do not get updated properly.
>
>We were wondering what other people are doing to ensure the database is
>on stand alone mode when doing your updates:
>These two things have been suggested to us:
>1) temporarily change the dba password while doing the update so no one can
>connect, then change it back after the update.
>2) Use the dbconsole utility to block any additional connections then run our
>update.
>
>Has anyone had success doing either, or do you do something altogether
>different?
>Any ideas would be appreciated!
>Thanks,
>L.Ford

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/ASIN/1556225067/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com


David Fishburn Posted on 2005-03-03 13:55:10.0Z
Newsgroups: ianywhere.public.general
Subject: Re: What is the best way to keep users out of the database during a database update?
From: David Fishburn <fishburn_spam@off.ianywhere.com>
References: <4225de93$1@forums-1-dub> <jj2c21hjl0ns9c2v47h8o7utqoj5vmtdg0@4ax.com>
Organization: iAnywhere Solutions
Message-ID: <Xns960E5AA66C41Ffishburnsybasecom@127.0.0.1>
User-Agent: Xnews/06.08.25 Hamster/2.0.6.0
NNTP-Posting-Host: vpn-concord-072.sybase.com
X-Original-NNTP-Posting-Host: vpn-concord-072.sybase.com
Date: 3 Mar 2005 05:55:10 -0800
X-Trace: forums-1-dub 1109858110 158.159.8.72 (3 Mar 2005 05:55:10 -0800)
X-Original-Trace: 3 Mar 2005 05:55:10 -0800, vpn-concord-072.sybase.com
Lines: 48
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:4194
Article PK: 8073

"Breck Carter [TeamSybase]" <NOSPAM__bcarter@risingroad.com> wrote in
news:jj2c21hjl0ns9c2v47h8o7utqoj5vmtdg0@4ax.com of
ianywhere.public.general:

BC> Do this Google Groups search...
BC>
BC> p_drop_other_connections group:sybase.public.sqlanywhere.*
BC>
BC> That procedure is also on
BC> http://ianywhere.codexchange.sybase.com/servlets/ProjectDocumentList
BC> ... do a search on sa_drop_other_connections in the ASA section.
BC>
BC> Instructions are contained inside the procedure, as comments.

Just before you use Breck's procedure then you can do this:

CALL sa_server_option( 'disable_connections', 'ON')
-- Do your schema changes
CALL sa_server_option( 'disable_connections', 'OFF')


See:
ASA SQL Reference
System Procedures and Functions
System and catalog stored procedures
sa_server_option system procedure

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm

Developer Community / Whitepapers
http://www.ianywhere.com/developer

CaseXpress - to report bugs
http://casexpress.sybase.com

CodeXchange - Free samples
http://ianywhere.codexchange.sybase.com/servlets/ProjectDocumentList