Groups | Blog | Home
all groups > sql server (alternate) > may 2004 >

sql server (alternate) : sql server sizing planning - architecture help



Ragu
5/13/2004 11:11:23 PM
Hi

I joined a project where 100,000 rows were added everyday. Now due to
additional customers the expectation is 2 million reocrds/day ie 10 GB worth
of textfiles. We have to estimate the hard disk, memory, # of CPUs etc.We
will have one yearworth of data in the db. Rest will be in tapes etc.

We will be using WIN2000, SQL Server2000.- Any comparable server sizing will
be appreciated.

1. Tohandle every day load, I thought that we will have a table for each day
(pre created in the database )and have a view with union all selecting
fromall these 365 tables. (This is the only way to partition in MSSQL Server
right?).

2. The requirement is to populate datawarehouse tables with all the data.
However there will be only inserts mostly but there can be updates too which
happenned in the past 12 days.Hence we have to use the data from the last
12 days and massage it etc and populate into datawarehouse tables.

How can I do this so that I will have the datawarehouse tables with n-12
days of data and I will alwys add the last 12 days data to it.

Do you have any suggestions?

Ragu


John Bell
5/15/2004 10:25:07 AM
Hi

Check out "Estimating the Size of a Database" in Books online:
mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\cre
atedb.chm::/cm_8_des_02_92k3.htm

mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\cre
atedb.chm::/cm_8_des_02_33js.htm

mk:@MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\cre
atedb.chm::/cm_8_des_02_2248.htm


John

[quoted text, click to view]

John Bell
5/15/2004 6:16:43 PM
Hi

In addition....

On one of the CDs accompanying "Inside SQL Server 2000" by Kalen Delany ISBN
0-7356-0998-5, there is a stored procedure which will give you the size.

John

[quoted text, click to view]

Erland Sommarskog
5/15/2004 10:00:27 PM
Ragu (ragudba@sbcglobal.net) writes:
[quoted text, click to view]

Yes, you set up a partitioned view over all this tables. Be careful
to apply your check constraints accordingly.

However, I'm in doubt that having one table per day is really a good
thing. Yes, loads will be fast, if the table is empty and clean
each day. But with a clustered index on date, you would append the
new rows at the end. One table per month seems more manageable....

[quoted text, click to view]

Too little information to say anything substantial, but a common technique
is to first load into a staging table, and then take it from there. Note
that for the previous days, you would need to do both and UPDATE and an
INSERT, presuming that new rows may appear too.

--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se

Books Online for SQL Server SP3 at
AddThis Social Bookmark Button