Hi all,
Some tables of a production DB (in an enterprise scenario) contain many
milions of rows ...
Is really advisable to create a custom dbspace for everyone of them ?
Does it produce performance improvements ?
Thanks.

Using additional dbspaces makes sense only when you can physically
separate the dbspaces onto separate disks, and thus control the
allocation of disk heads to the database as a whole. If you're using a
single disk, or a RAID or NAS back-end, there is little point to using
dbspaces unless you're running into the maximum size of a file on your
platform (Windows?), which is very large.

Glenn

Nicola Cisternino wrote:
--
Glenn Paulley
Director, Engineering (Query Processing)
Sybase iAnywhere

Blog: http://iablog.sybase.com/paulley

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports: http://case-express.sybase.com

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the
Sybase iAnywhere pages at
http://www.sybase.com/products/datab...chnicalsupport

In article <4adb6e4b$1@forums-1-dub>, ncisternino (AT) gmail (DOT) com says...
How many million? I have two tables of 6M - 10M rows each in a single
production DB, and have no trouble keeping everything in a single file
on a single (RAIDed) HD.


--
/~\ The ASCII
\ / Ribbon Campaign
X Against HTML
/ \ Email!

Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).