How big is Big? Size of Enterprise Databases.

Question

How big is Big? Size of Enterprise Databases.

nileshsane

Default port

Points: 1465
More actions
May 15, 2006 at 3:54 am

#90907

I know that this is a very open ended question.
What we are trying to do is prepare a configuration(in size) for a database, which would be termed as an enterprise database. For example, we cannot term a 20 MB database big enough for enterprise wide implementations.
We are basically looking at populating a database with test data and run some performance tests on it. The results of these tests would kind of give us some idea of how the system works with databases with hugh/large data volumes. We don't know where to start from, but the idea is to set up a database whose size would be close to databases, which would be in use in big companies.
Our system is primarily read centric with about 70% of the queries being selects. Database usage patterns from our previous installations have been such that the max database size, which we have reached over a period of 3-4 years, is 500 MB (MDF size). The new system is considerably more complex and I foresee that size being reached in a single year. Once could say that I have answered my question for myself but I just want to make sure that the system would still work OK when it is scaled up to levels which are found in big Enterprises.
What I hear I forget, what I see I remember, what I do I understand

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Martin Schoombee SSCoach Points: 19128 More actions · Answer 1

Hi,

This is a difficult question to answer and is very specific to the kind of system and business you find yourself in. In my opinion anything that gets to the 1TB region is big...

To give you an idea, we currently have a datawarehouse sitting at about 600GB. We are still loading history, and estimate it to be about 1.2TB when all the history is loaded. But keep in mind that this is a datawarehouse.

At the end it all depends on how many transactions you anticipate in a month/year, and how much history you would like to keep before archiving. If you are not sure, take your current scenario and multiply it by 10. You might think that this is way too much, but nowadays with complex systems and databases it might not be that far off.

Hope this helps,

Martin.

nileshsane Default port Points: 1465 More actions · Answer 2

Thanks for the reply, it did help.

I have additionally found that Microsoft recommends the usage of their

Enterprise Edition (SQL Server 2000) [Source: http://www.microsoft.com/technet/community/chats/trans/sql/sql0326.mspx]

for dbs which are over 2 GB in size and term a database of 500 GB as a VLDB.

The db which you have is a VVLDB.

Thanks again.

What I hear I forget, what I see I remember, what I do I understand

Martin Schoombee SSCoach Points: 19128 More actions · Answer 3

Yep, we indeed have a VVLDB...and it makes management and maintainance very interesting. Simple operations take forever because of the pure size of it, and planning becomes essential for even the smallest tasks.

Good luck

Eoin The Forge SSCrazy Points: 2932 More actions · Answer 4

Hey,

I think that the 2Gig figure is the max amount of RAM that is useable for the standard version. If you want to use >2Gig of ram, you then move to enterprise ed (Or upgrade to 2005)

Eoin

nileshsane Default port Points: 1465 More actions · Answer 5

Could be but the context in which it was said made me believe that it was with relation to the disk size of the database. Besides this was a conversation about Very Large Database (VLDB) and SQL Server, hence the assumption.

I quote a part of the conversation from http://www.microsoft.com/technet/community/chats/trans/sql/sql0326.mspx

Host: Richard (Microsoft)

Q: Any change of more versions or SQL? More al la carte of features? For example, we'd like to go to 8GB on some servers, but we don't need all the enterprise features. Or any other of them. Cost is starting to become an issue, especially compared to dB2.

A: Anything > 2GB is Enterprise Edition only. On the cost issue are you including all features (tools, etc.)? Also look at http://www.microsoft.com/sql/evaluation/compare/IBM/DB2v8.asp

What I hear I forget, what I see I remember, what I do I understand

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 6

SQL Server 'Standard' - supports a maximum of 2 Gb or RAM for SQL Server only.

SQL Server 'Enterprise' - supports more than of 2 Gb or RAM (up to 64 Gb I believe, is used for clustering and has log shipping built in. I'm sure if you search MS or MSDN you can find the 'features comparison' page for the available versions.

In your initial example though, you kind of equate 'size' with 'enterprise' as if the 2 are directly related, but I think not in most situations. 'enterprise' is something the entire organization uses. As an example our key card access system for 19 locations and 2500 people is only 200 Mb - this is an 'enterprise' software/database applciation. Now we have an operational reporting database used only by IT, this is not used by the entire 'enterprise' (only 7 ITY staff members), and the database is almost 500 Gb.

So database size is one particular aspect and the usage of the application and database is another (whole organization is 'enterprise' wide' or a smaller user community).

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Ian Yates SSCoach Points: 19738 More actions · Answer 7

And the quoted discussion is DEFINITELY talking about memory being 2GB limit, not DB disk size - although that happens to be the limit for DB sizes in MSDE

The performance also comes down to things such as indices present for joins, what sort of columns are indexed, etc.. Also how often you defrag an index for such a HUGE HUGE database could play a big part both in maintenance downtime and day-to-day select performance.

nileshsane Default port Points: 1465 More actions · Answer 8

Thanks a Ton guys. Your points made me clear some misconceptions about "Size".

What I hear I forget, what I see I remember, what I do I understand