home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.sybase
- Path: sparky!uunet!shearson.com!newshost!wfinnert
- From: wfinnert@larry.shearson.com (Warren Finnerty)
- Subject: Re: Sybase Data Page Allocation
- In-Reply-To: phil@n6batws1.itwol.bhp.com.au's message of 7 Jan 93 10:36:33 +1000
- Message-ID: <WFINNERT.93Jan7092037@larry.shearson.com>
- Sender: news@shearson.com (News)
- Organization: Lehman Brothers
- References: <1993Jan7.103634.268@vulcan.resmel.bhp.com.au>
- Date: Thu, 7 Jan 1993 14:20:37 GMT
- Lines: 32
-
- In article <1993Jan7.103634.268@vulcan.resmel.bhp.com.au> phil@n6batws1.itwol.bhp.com.au (Phil McMillan) writes:
-
-
- > I have a question regarding the allocation of the 2kbyte data pages when they
- > become "reserved" by tables.
- >
- > Assume I have a table that typically contains, say, 1000 rows. If I then for some
- > reason add an extra 30,000 rows I obviously will take more than a few data pages
- > from the pool of storage (and at least 8 of them.)
-
- > From what I understand, these data pages (for indexes and rows) are now owned,
- > or reserved, by the table.
-
- > If I delete these 30,000 rows, will/should these data pages become returned to
- the pool?
-
-
- Yes.
-
- If you have a clustered index on the table there should be no problem with
- freeing up space. However......
- Don't trust sysindexes unless DBCC checktable ( or checkdb ) gets run.
- If your deletes remove a percentage of the data from each page, but don't
- completely *no* space will be reclaimed because you have not freed
- any pages up. Bottom line: Leave time every month or so to bounce your
- clustered indexes down/up and things will be a lot cooler.
-
- --
- warren finnerty | 388 Greenwich St.
- Lehman Brothers | NYC NY 10013
- "Back off man!" | wfinnert@shearson.com
-
-