RE: RE: Locally Managed Tablespaces

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Fri, 21 Mar 2003 16:03:23 -0800
Message-Id: <24738.322758@fatcity.com>

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2F006.74C39540
Content-Type: text/plain

> -----Original Message-----
> From: Jared.Still_at_radisys.com [mailto:Jared.Still_at_radisys.com]
> 
> I think my 'reasonable' # of extents must be higher than 
> yours Jacques. :)

I agree that having a datafile autoextend is better than having a job die. On the other hand a poorly written job that runs amuck can be stopped before creating too much damage if you set limits on your datafile sizes. But yes, autoextend definitely has its uses. As far as my suggested maximum of 1000 extents: some people give me grief about that. I have worked mostly in development environments and so I might be out of touch. But 1000 extents should be plenty for anybody. When is the last time you had to drop a table with 10000 extents, and have the developer looking over your shoulder tell you "In Access when you drop a table it's instantaneous?"

------_=_NextPart_001_01C2F006.74C39540
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>RE: RE: Locally Managed Tablespaces</TITLE>
</HEAD>
<BODY>

> -----Original Message-----
 > From: Jared.Still_at_radisys.com [<A =
HREF=3D"mailto:Jared.Still_at_radisys.com">mailto:Jared.Still_at_radisys.com</= A>]
 > 
 > I think my 'reasonable' # of extents must be =
higher than 
 > yours Jacques. :)

 

I agree that having a datafile autoextend is better =
than having a job die. On the other hand a poorly written job that runs = amuck can be stopped before creating too much damage if you set limits = on your datafile sizes.

But yes, autoextend definitely has its uses.
 As far as my suggested maximum of 1000 extents: some =
people give me grief about that. I have worked mostly in development = environments and so I might be out of touch. But 1000 extents should be = plenty for anybody. When is the last time you had to drop a table with = 10000 extents, and have the developer looking over your shoulder tell = you "In Access when you drop a table it's = instantaneous?" Received on Fri Mar 21 2003 - 18:03:23 CST