How big on SQL Server? 
Author Message
 How big on SQL Server?

 How far can you push SQL Server 7 before you start hitting the
"bleeding" edge?  I'm running SQL Server 7 on an HP LH3 with 4
processors and 4 Gigs of RAM.  We are using Informatica for ETL with
ascii source files.  We are getting about 1.5 Gig of data per day (about
50 million rows).  I expect that to go to 3 Gig/day in December.  I'm
summarizing the data into a single fact table that hist 2Gig / 20
million rows in a month,  once the summaries are generated I discard the
transaction level detail.  The current rollout plan is to add another
market each month for the next 12 months, a WAG is that those markets
will generate between 1.5 and 4 Gig of transaction detail each.  I think
the company was hoping to clone the original db every 2 or 3 markets.

I come from an Oracle/Unix background and I think we ought to just bite
the bullet and go with unix and some serious hardware.In my mind it's
still a terabyte database even if we throw away the transaction detail
after we use it.  If nothing else the change control and source file
dispatching would become unmanageable.

 Any comments from people running really big db's?  In particular, at
what point (db size, table size / row count) do you start to hit the
wall with NT/SQL Server?


to respond, remove _removeword  from the email address.



Wed, 24 Apr 2002 03:00:00 GMT
 How big on SQL Server?

Holly - I wouldn't describe what you've got as bleeding edge.  As long as
you've got a high-end disk and backup subsystem then you should be fine with
SQL 7.

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please reply only to newsgroups)
 SQL FAQ (356 entries) see

 or www.ntfaq.com/sql.html (+ ntfaq download)
 or http://www.swynk.com/faq/sql/sqlserverfaq.asp
 or http://www.sql-server.co.uk



Thu, 25 Apr 2002 03:00:00 GMT
 How big on SQL Server?
Hi Holly,

I recently spent some time working on the MS Press Deployment Guide for SQL
Server 7.0, Notes from the Field.  I interviewed lots of large accounts
throughtout the U.S. using SQL Server.  One of the accounts interviewd was
Unisys.  Check out http://www.unisys.com/sql7/demo.html.  They have the
largest (at least a year ago they did) SQL Server "Business" Database in the
world.  2.5 Terrabytes of Data and another 1.5 Terrabytes of Indexes.
Running good.  You can actually browse the data online..:)

Thanks,

Frank Abendroth
DVMB AG
Germany


Quote:
> How far can you push SQL Server 7 before you start hitting the
> "bleeding" edge?  I'm running SQL Server 7 on an HP LH3 with 4
> processors and 4 Gigs of RAM.  We are using Informatica for ETL with
> ascii source files.  We are getting about 1.5 Gig of data per day (about
> 50 million rows).  I expect that to go to 3 Gig/day in December.  I'm
> summarizing the data into a single fact table that hist 2Gig / 20
> million rows in a month,  once the summaries are generated I discard the
> transaction level detail.  The current rollout plan is to add another
> market each month for the next 12 months, a WAG is that those markets
> will generate between 1.5 and 4 Gig of transaction detail each.  I think
> the company was hoping to clone the original db every 2 or 3 markets.

> I come from an Oracle/Unix background and I think we ought to just bite
> the bullet and go with unix and some serious hardware.In my mind it's
> still a terabyte database even if we throw away the transaction detail
> after we use it.  If nothing else the change control and source file
> dispatching would become unmanageable.

>  Any comments from people running really big db's?  In particular, at
> what point (db size, table size / row count) do you start to hit the
> wall with NT/SQL Server?


> to respond, remove _removeword  from the email address.



Fri, 26 Apr 2002 03:00:00 GMT
 How big on SQL Server?
 Actually, it's Terry (Stover).  I didn't realize my wife had changed the
preferences on the newsreader.

Pretty impressive installation, response time is great too.  At this stage I
would consider any solution that involves clustering to the proof of concept /
technically possible category (guaranteed to deliver high consulting fees).
It's amazing what a truly knowledgeable system architect/dba can do.

Quote:

> I recently spent some time working on the MS Press Deployment Guide for SQL
> Server 7.0, Notes from the Field.  I interviewed lots of large accounts
> throughtout the U.S. using SQL Server.  One of the accounts interviewd was
> Unisys.  Check out http://www.unisys.com/sql7/demo.html.  They have the
> largest (at least a year ago they did) SQL Server "Business" Database in the
> world.  2.5 Terrabytes of Data and another 1.5 Terrabytes of Indexes.
> Running good.  You can actually browse the data online..:)

> Thanks,

> Frank Abendroth
> DVMB AG
> Germany



> > How far can you push SQL Server 7 before you start hitting the
> > "bleeding" edge?  I'm running SQL Server 7 on an HP LH3 with 4
> > processors and 4 Gigs of RAM.  We are using Informatica for ETL with
> > ascii source files.  We are getting about 1.5 Gig of data per day (about
> > 50 million rows).  I expect that to go to 3 Gig/day in December.  I'm
> > summarizing the data into a single fact table that hist 2Gig / 20
> > million rows in a month,  once the summaries are generated I discard the
> > transaction level detail.  The current rollout plan is to add another
> > market each month for the next 12 months, a WAG is that those markets
> > will generate between 1.5 and 4 Gig of transaction detail each.  I think
> > the company was hoping to clone the original db every 2 or 3 markets.

> > I come from an Oracle/Unix background and I think we ought to just bite
> > the bullet and go with unix and some serious hardware.In my mind it's
> > still a terabyte database even if we throw away the transaction detail
> > after we use it.  If nothing else the change control and source file
> > dispatching would become unmanageable.

> >  Any comments from people running really big db's?  In particular, at
> > what point (db size, table size / row count) do you start to hit the
> > wall with NT/SQL Server?


> > to respond, remove _removeword  from the email address.

--

to respond, remove _removeword  from the email address.


Fri, 26 Apr 2002 03:00:00 GMT
 How big on SQL Server?
I would stick with SQL7 and NT. Best BANG for your Buck..:)


Quote:
> Actually, it's Terry (Stover).  I didn't realize my wife had changed the
> preferences on the newsreader.

> Pretty impressive installation, response time is great too.  At this stage
I
> would consider any solution that involves clustering to the proof of
concept /
> technically possible category (guaranteed to deliver high consulting
fees).
> It's amazing what a truly knowledgeable system architect/dba can do.

> > I recently spent some time working on the MS Press Deployment Guide for
SQL
> > Server 7.0, Notes from the Field.  I interviewed lots of large accounts
> > throughtout the U.S. using SQL Server.  One of the accounts interviewd
was
> > Unisys.  Check out http://www.unisys.com/sql7/demo.html.  They have the
> > largest (at least a year ago they did) SQL Server "Business" Database in
the
> > world.  2.5 Terrabytes of Data and another 1.5 Terrabytes of Indexes.
> > Running good.  You can actually browse the data online..:)

> > Thanks,

> > Frank Abendroth
> > DVMB AG
> > Germany



> > > How far can you push SQL Server 7 before you start hitting the
> > > "bleeding" edge?  I'm running SQL Server 7 on an HP LH3 with 4
> > > processors and 4 Gigs of RAM.  We are using Informatica for ETL with
> > > ascii source files.  We are getting about 1.5 Gig of data per day
(about
> > > 50 million rows).  I expect that to go to 3 Gig/day in December.  I'm
> > > summarizing the data into a single fact table that hist 2Gig / 20
> > > million rows in a month,  once the summaries are generated I discard
the
> > > transaction level detail.  The current rollout plan is to add another
> > > market each month for the next 12 months, a WAG is that those markets
> > > will generate between 1.5 and 4 Gig of transaction detail each.  I
think
> > > the company was hoping to clone the original db every 2 or 3 markets.

> > > I come from an Oracle/Unix background and I think we ought to just
bite
> > > the bullet and go with unix and some serious hardware.In my mind it's
> > > still a terabyte database even if we throw away the transaction detail
> > > after we use it.  If nothing else the change control and source file
> > > dispatching would become unmanageable.

> > >  Any comments from people running really big db's?  In particular, at
> > > what point (db size, table size / row count) do you start to hit the
> > > wall with NT/SQL Server?


> > > to respond, remove _removeword  from the email address.

> --

> to respond, remove _removeword  from the email address.



Thu, 02 May 2002 03:00:00 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. BIG MS SQL SERVER DATABASE

2. Log Too Big on SQL Server 6.5

3. Big MS SQL Server 6.5 Bug

4. BIG, BIG, BIG, BIG problem with SQL Server 2000 ENT. SP2 installed on Windows 2000 server when use xp_SendMail, xp_StartMail

5. Server Selection and SQL Server for BIG Databases

6. Big Trouble With Sybase SQL Server and VB5 client-server application

7. How big is too big for MS SQL database

8. sql server performance with big web site...

9. Access -> SQL Server = BIG DB

10. Big databases with SQL server

11. US - Nationwide - Big 6 - IT Consultants - SQL Server

12. Access 97/SqlServer 7: Appending Access Tables into Sql Server tables doesnt work for big tables


 
Powered by phpBB® Forum Software