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.

More Control Of Space Allocation For Objects

5 posts in Product Futures Discussion Last posting was on 2003-03-30 19:00:38.0Z
putnamr Posted on 2003-03-23 02:12:44.0Z
From: putnamr@river.it.gvsu.edu
Date: Sat, 22 Mar 2003 21:12:44 -0500
Newsgroups: sybase.public.ase.product_futures_discussion
Subject: More Control Of Space Allocation For Objects
Message-ID: <7C044B0F1251635D000C26EC85256CF2.000C271B85256CF2@webforums>
Lines: 36
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1040
Article PK: 95286

Hello,

I would like to be able further control the space allocation for objects by
specifying LSTART ranges for objects on whatever devices or segments those
objects are located on.

For example)
CREATE TABLE TABLE_A (COL_A ...)
ON seg001
USING LSTART RANGE 65536 TO 262144
USING LSTART RANGE 524288 TO 1048576
ETC...
go

So,
New system tables:
-- For Object Specific Space Management
sysgrowthplan (id int not null, -- Object Id
low int not null, -- Low Lstart Value
high int not null, -- High Lstart Value
segmap int not null, -- Segmap Info For Object
device_num int not null) -- Device Number
PK(id, device_num, segmap, low, high)

-- Lstart Range To Exclude For All Objects Except For Those
-- Defined In sysgrowthplan
sysgrowthexclude (low int not null, -- Low Lstart Value
high int not null, -- High Lstart Value
segmap int not null, -- Segmap Info For Object
device_num int not null) -- Device Number
PK(device_num, segmap, low, high)

Is this possible?

Thanks,
Ryan Putnam


KR Posted on 2003-03-29 18:12:49.0Z
Reply-To: "KR" <zzb26@mail.com.NOJUNK>
From: "KR" <zzb26@mail.com.NOJUNK>
References: <7C044B0F1251635D000C26EC85256CF2.000C271B85256CF2@webforums>
Subject: Re: More Control Of Space Allocation For Objects
Date: Sat, 29 Mar 2003 19:12:49 +0100
Lines: 49
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <#TTzR9h9CHA.313@forums-2-dub>
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: m57.net81-65-230.noos.fr 81.65.230.57
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1077
Article PK: 95315

I think it is very important that Sybase keeps its products easy to use, yet
powerful. I don't really see your idea beeing all that useful. There are
currently far more important features that Sybase should work on. I believe
that converting the system tables to Row Level Locking is one of them.

kr

<putnamr@river.it.gvsu.edu> wrote in message
news:7C044B0F1251635D000C26EC85256CF2.000C271B85256CF2@webforums...
> Hello,
>
> I would like to be able further control the space allocation for objects
by
> specifying LSTART ranges for objects on whatever devices or segments those
> objects are located on.
>
> For example)
> CREATE TABLE TABLE_A (COL_A ...)
> ON seg001
> USING LSTART RANGE 65536 TO 262144
> USING LSTART RANGE 524288 TO 1048576
> ETC...
> go
>
> So,
> New system tables:
> -- For Object Specific Space Management
> sysgrowthplan (id int not null, -- Object Id
> low int not null, -- Low Lstart Value
> high int not null, -- High Lstart Value
> segmap int not null, -- Segmap Info For Object
> device_num int not null) -- Device Number
> PK(id, device_num, segmap, low, high)
>
> -- Lstart Range To Exclude For All Objects Except For Those
> -- Defined In sysgrowthplan
> sysgrowthexclude (low int not null, -- Low Lstart Value
> high int not null, -- High Lstart Value
> segmap int not null, -- Segmap Info For Object
> device_num int not null) -- Device Number
> PK(device_num, segmap, low, high)
>
> Is this possible?
>
> Thanks,
> Ryan Putnam


putnamr Posted on 2003-03-29 23:02:21.0Z
From: putnamr@river.it.gvsu.edu
Date: Sat, 29 Mar 2003 18:02:21 -0500
Newsgroups: sybase.public.ase.product_futures_discussion
Subject: Re: More Control Of Space Allocation For Objects
Message-ID: <CC9188BDFFDDD682007E8ECB85256CF8.0069182B85256CF8@webforums>
References: <7C044B0F1251635D000C26EC85256CF2.000C271B85256CF2@webforums> <#TTzR9h9CHA.313@forums-2-dub>
Lines: 2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1081
Article PK: 95320

Actually, this is important because it can help eliminate fragmentation at
the extent level and thus increase IO throughput, very important for DSS.


Bret Halford Posted on 2003-03-30 15:17:28.0Z
Message-ID: <3E870A88.B4E5A328@sybase.com>
Date: Sun, 30 Mar 2003 08:17:28 -0700
From: Bret Halford <bret@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: More Control Of Space Allocation For Objects
References: <7C044B0F1251635D000C26EC85256CF2.000C271B85256CF2@webforums> <#TTzR9h9CHA.313@forums-2-dub> <CC9188BDFFDDD682007E8ECB85256CF8.0069182B85256CF8@webforums>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.ase.product_futures_discussion
NNTP-Posting-Host: vpn-dub-060.sybase.com 10.22.120.60
Lines: 17
Path: forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1084
Article PK: 95321

This is largely what segments already do (though admittedly without
quite as
much flexibility and a few more limits) - and I've seen ony a few
customers that
had actually hit the limit on number of segments in a database (32). It
would
probably be easier to increase the limit on the number of segments than
introduce
new command syntax like this. Stored procedures could be created
that could split fragments and assign segments based on lstart ranges.

-bret

putnamr@river.it.gvsu.edu wrote:
>
> Actually, this is important because it can help eliminate fragmentation at
> the extent level and thus increase IO throughput, very important for DSS.


putnamr Posted on 2003-03-30 19:00:38.0Z
From: putnamr@river.it.gvsu.edu
Date: Sun, 30 Mar 2003 15:00:38 -0400
Newsgroups: sybase.public.ase.product_futures_discussion
Subject: Re: More Control Of Space Allocation For Objects
Message-ID: <897CC238308E6F0C00686DB385256CF9.005ACF0885256CF9@webforums>
References: <7C044B0F1251635D000C26EC85256CF2.000C271B85256CF2@webforums> <#TTzR9h9CHA.313@forums-2-dub> <CC9188BDFFDDD682007E8ECB85256CF8.0069182B85256CF8@webforums> <3E870A88.B4E5A328@sybase.com>
Lines: 1
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1085
Article PK: 95323

That would be a great way to do this.