I have a 900gb drive that is being dedicated to my new database. Please, I
need in determining the correct sizing starting of so I don't end up
with disk fragmentation issues later.

Thanks,
KenO

KenO,

You need to know your data, how many rows you expect in each table, how wide
those rows are, how many indexes, et cetera. Then you can add up your
numbers and estimate for the overall database. These links are those that
Microsoft published (in the SQL Server 2000 Books Online) to think
through the question:

http://msdn2.microsoft.com/en-us/lib...4(SQL.80).aspx Estimating
database size
http://msdn2.microsoft.com/en-us/lib...8(SQL.80).aspx Estimating
table size

I would suggest that you at least double your initial size estimate and then
plan for database growth so that you will not be frequently growing. If you
can grow your database only every 6 to 12 months then whatever size that is
for you should keep there from being a lot of fragmentation on the database
files.

Also, plan the transaction log size accordingly. Some recommend half the
size of the database, but that may be excessive on a very large, but slowly
changing database. Again, you need to know (or best guess) the behaviour
expected from your database.

Not a direct answer perhaps, but I hope it gets you started. There are
people out there who run bigger databases than I do, so they may have some
greater wisdom to share.

RLF



"KenO" <KenO@discussions.microsoft.com> wrote in message
news:7B1E0617-77E4-47C0-A615-447570C98A2B@microsoft.com...
>I have a 900gb drive that is being dedicated to my new database. Please, I
> need in determining the correct sizing starting of so I don't end up
> with disk fragmentation issues later.
>
> Thanks,
> KenO