Also how might it relate to Page Size in SQL Anywhere.

Thanks!

asked 22 Jul '11, 09:05

ivankb's gravatar image

ivankb
265101121
accept rate: 50%


Take a look at my answer to a similar question that asked about what NTFS allocation size should be used for an 8k database page size.

Short answer is that it doesn't really matter if you are not that concerned about getting optimal performance. If you want best performance and best probability that your file system is not going to corrupt your database file then it is likely best to match your page size to the file system page size (and natural disk sector size).... but you need to be careful if your file system sector size is too large (16K or 32K) since other effects can kick in - e.g. wasted cache memory due to using a page size which is too large for your database schema and application usage pattern. I.e. if your file system sector size is 16K or 32K then I would suggest that you do a performance evaluation between using a 16K (or 32K) database page size and an 8k (and/or 4K) page size.

permanent link

answered 22 Jul '11, 09:33

Mark%20Culp's gravatar image

Mark Culp
22.7k9129266
accept rate: 40%

edited 22 Jul '11, 16:31

Thanks, I did see and read that answer after posting! Now I need to do some leg work to see what DB page size is ideal for my case then select an appropriate cluster size from that.

(22 Jul '11, 09:57) ivankb
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×8
×7
×4
×1

question asked: 22 Jul '11, 09:05

question was seen: 5,370 times

last updated: 22 Jul '11, 16:31