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.

Shrinking Database

4 posts in Product Futures Discussion Last posting was on 2003-09-29 00:14:17.0Z
Leonardo Pasta Posted on 2003-07-03 14:50:26.0Z
From: "Leonardo Pasta" <lhpasta@performinformatica.com.br>
Subject: Shrinking Database
Date: Thu, 3 Jul 2003 11:50:26 -0300
Lines: 10
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <uSs9OOXQDHA.317@forums-2-dub>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: 200.203.179.70
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1270
Article PK: 95510

I kown it isn't a trivial feature, but I would love to see a Shrink
Database option on ASE.
Is there any plans on work on that? Or any easy way of accomplish that
tasks? I'm not considering ddlgen + bcp in/out, etc. I already do it when I
need, but I cannot call it a easy way of dealing with this change

Thanks in advance,
Leonardo Pasta


Bret Halford Posted on 2003-07-04 15:48:01.0Z
Message-ID: <3F05A1B1.320626FA@sybase.com>
Date: Fri, 04 Jul 2003 09:48:01 -0600
From: Bret Halford <bret@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
Subject: Re: Shrinking Database
References: <uSs9OOXQDHA.317@forums-2-dub>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: vpn-dub-051.sybase.com 10.22.120.51
Lines: 34
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1273
Article PK: 95513


Leonardo Pasta wrote:
>
> I kown it isn't a trivial feature, but I would love to see a Shrink
> Database option on ASE.
> Is there any plans on work on that? Or any easy way of accomplish that
> tasks? I'm not considering ddlgen + bcp in/out, etc. I already do it when I
> need, but I cannot call it a easy way of dealing with this change
>
> Thanks in advance,
> Leonardo Pasta

There is an open feature request for this, CR 171236. The main
difficulty is that
there are certain objects in a database that cannot easily be moved,
such as
system tables that don't have a clustered index (such as sysgams) or
sysindexes
(whose clustered index cannot be rebuilt), and text/image allocations.

There is a technique for shrinking databases documented at
http://www.isug.com/Sybase_FAQ/ASE/section1.2.html#1.2.12. The
technique works
well unless you hit one of the cases mentioned above; depending on facts
and
circumstances it can be much easier than ddlgen and bcp (i.e. it is
quite easy
to lop off the last fragment of a database when it is a log fragment,
but with a
data fragment you may have to rebuild clustered indexes on many tables
to accomplish it,
and if you hit something that can't be moved, then you are left with the
ddlgen and bcp
technique).

-bret


Arun Posted on 2003-07-19 00:01:08.0Z
From: "Arun" <arun.patnaik@sybase.com>
References: <uSs9OOXQDHA.317@forums-2-dub> <3F05A1B1.320626FA@sybase.com>
Subject: Re: Shrinking Database
Date: Fri, 18 Jul 2003 17:01:08 -0700
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4922.1500
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4925.2800
Message-ID: <#KMXMoYTDHA.298@forums-2-dub>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: arupatw2k.sybase.com 10.22.90.118
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1309
Article PK: 95547

In case anyone decides on following the 'unsupported shrink database'
mechanism as mentioned in the mentioned technote, please note that you will
NOT be able to use the disk reinit/disk refit mechanism of disaster
recovery.

BTW, how would people feel if the disk reinit/disk refit support was absent
? Just trying to understand how desirable these commands are in todays
environment.

Thanks
- Arun

"Bret Halford" <bret@sybase.com> wrote in message
news:3F05A1B1.320626FA@sybase.com...
> There is an open feature request for this, CR 171236. The main
> difficulty is that
> there are certain objects in a database that cannot easily be moved,
> such as
> system tables that don't have a clustered index (such as sysgams) or
> sysindexes
> (whose clustered index cannot be rebuilt), and text/image allocations.
>
> There is a technique for shrinking databases documented at
> http://www.isug.com/Sybase_FAQ/ASE/section1.2.html#1.2.12. The
> technique works
> well unless you hit one of the cases mentioned above; depending on facts
> and
> circumstances it can be much easier than ddlgen and bcp (i.e. it is
> quite easy
> to lop off the last fragment of a database when it is a log fragment,
> but with a
> data fragment you may have to rebuild clustered indexes on many tables
> to accomplish it,
> and if you hit something that can't be moved, then you are left with the
> ddlgen and bcp
> technique).
>
> -bret


"Jeff" <jboyce2 Posted on 2003-09-29 00:14:17.0Z
From: "Jeff" <jboyce2@comcast_dot_net>
Newsgroups: sybase.public.ase.product_futures_discussion
References: <uSs9OOXQDHA.317@forums-2-dub> <3F05A1B1.320626FA@sybase.com> <#KMXMoYTDHA.298@forums-2-dub>
Subject: Re: Shrinking Database
Lines: 53
Organization: forums.sybase.com
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: bgp480984bgs.summit01.nj.comcast.net
X-Original-NNTP-Posting-Host: bgp480984bgs.summit01.nj.comcast.net
Message-ID: <3f777959$1@forums-1-dub>
Date: 28 Sep 2003 17:14:17 -0700
X-Trace: forums-1-dub 1064794457 68.37.160.251 (28 Sep 2003 17:14:17 -0700)
X-Original-Trace: 28 Sep 2003 17:14:17 -0700, bgp480984bgs.summit01.nj.comcast.net
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1400
Article PK: 96407

I have never used disk re-fit/re-init, and I routinely shrink databases as
described in the ISUG FAQ. I have never been concerned with not being able
to do disk refir/init, but maybe its just because I dont understand how they
can be usefull. Never seemed like the route I would like to take during
recovery...

JBoyce

"Arun" <arun.patnaik@sybase.com> wrote in message
news:%23KMXMoYTDHA.298@forums-2-dub...
> In case anyone decides on following the 'unsupported shrink database'
> mechanism as mentioned in the mentioned technote, please note that you
will
> NOT be able to use the disk reinit/disk refit mechanism of disaster
> recovery.
>
> BTW, how would people feel if the disk reinit/disk refit support was
absent
> ? Just trying to understand how desirable these commands are in todays
> environment.
>
> Thanks
> - Arun
> "Bret Halford" <bret@sybase.com> wrote in message
> news:3F05A1B1.320626FA@sybase.com...
> > There is an open feature request for this, CR 171236. The main
> > difficulty is that
> > there are certain objects in a database that cannot easily be moved,
> > such as
> > system tables that don't have a clustered index (such as sysgams) or
> > sysindexes
> > (whose clustered index cannot be rebuilt), and text/image allocations.
> >
> > There is a technique for shrinking databases documented at
> > http://www.isug.com/Sybase_FAQ/ASE/section1.2.html#1.2.12. The
> > technique works
> > well unless you hit one of the cases mentioned above; depending on facts
> > and
> > circumstances it can be much easier than ddlgen and bcp (i.e. it is
> > quite easy
> > to lop off the last fragment of a database when it is a log fragment,
> > but with a
> > data fragment you may have to rebuild clustered indexes on many tables
> > to accomplish it,
> > and if you hit something that can't be moved, then you are left with the
> > ddlgen and bcp
> > technique).
> >
> > -bret
>
>