• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 190
  • Last Modified:

sql server size

Hi,
After installation of sql server 2005, as a DBA how could we estimate the size of the database to be created.
what is the best practise followed in real time scenario .
0
dotnet0824
Asked:
dotnet0824
  • 5
  • 5
  • 3
  • +2
3 Solutions
 
giltjrCommented:
Um, well it is fairly simple.  Just add up the total number of bytes needed for the database.

Of course in order to do this you would need to know the logical design of the database, number of tables, number of records in each table, all of the columns in each table, the type of data in each column, and the size of each column.

Here is an MSDN article http://msdn.microsoft.com/en-us/library/ms187445.aspx




0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
This would help you find the size of your database objects, thus helping you to estimate the database size in future..

http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1313431,00.html

Note: Free registration is required to view the complete contents in the above link..
0
 
dotnet0824Author Commented:
lets say we just joined a new set up company as a DBA and we have no data yet then how could we know

1) The size of data files
2) the memory required for the server
3) Number of processors etc.

Any good links available which would explain clearly considering this kind of scenario?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Anthony PerkinsCommented:
>>lets say we just joined a new set up company as a DBA and we have no data yet then how could we know <<
Unless you have some idea of the potential size of the tables and number of transactions you cannot know.  All you can do as a DBA is attempt to guage and do your best to make sure that you have built as scalable a platform as possible.  This comes from experience.  No amount of estimates and calculations will help you here.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> we have no data yet then how could we know

Ideally you can do an approximate calculation if you know

* how many lookup (Static - No new records) tables are there in your database
* how much records would go into each and every table ( this varies for each and every table)
* how many nullable columns are there in your database tables since that would also disturb your calculations..

In simple words, just work with the person who designed or modeled that Database to get complete information about that so that your calculation is precise...

Without which I would say that it wont be accurate..
0
 
giltjrCommented:
You can't est. the size of something if you have no details.



0
 
RiteshShahCommented:
>>lets say we just joined a new set up company as a DBA and we have no data yet then how could we know

1) The size of data files
2) the memory required for the server
3) Number of processors etc.<<

first you have to collect some details about what will be the use of database? what application will be using your database? how many tables will be there? how many user will concurrently access database? there are many more but these are basic.

Once you have an idea about these questions you can estimate the size of database, server capacity etc. until then nothing can be decided.

0
 
dotnet0824Author Commented:

"first you have to collect some details about what will be the use of database? what application will be using your database? how many tables will be there? how many user will concurrently access database? there are many more but these are basic.

Once you have an idea about these questions you can estimate the size of database, server capacity etc. until then nothing can be decided."


Q) Assuming that we have these details how could we estimate. Is there any examples online .
for eg : lets say as per what you say  there are 100 Tables, 20 concurrent users etc then how. I am looking for an example just to get a fair idea.





0
 
RiteshShahCommented:
well, this is not something I can explain in one answer as it depends on so many factor, even you can get an idea from below link.

http://sqlcommunity.com/Blogs/tabid/70/EntryId/28/How-to-estimate-disk-space-needed-for-SQL-Server.aspx

BTW, you said you may have 100 tables and 20 users. this is not enough, how many fields of those tables? what would be the datatype and what would the growth rate of data approximately etc. are needed.
0
 
giltjrCommented:
You are missing so much data.  You can't even being to try and guess at what you need.

Is this for real job?  Or is this some type of intro to database class?

If this is a for a real job and they really expect you, as a brand new DBA, to be able to est. the size and performance requirements or a database knowing nothing about the database or its usage, then RUN, RUN as fast as you can away from there.  

If this is for a class, just let us know and we can guide you, but a lot of the links that have been provide do give you the basics of est. database sizes.
0
 
dotnet0824Author Commented:
well I would be going ahead within few months as a Jr DBA, so just wanted to know about how in real time these things r tackled considering database design right from the scratch. What r the guideliness to be followed regarding estimation etc before creating the DB. Hope its clear now.
0
 
giltjrCommented:
Well the links provided give you the basics.

You start with table sizes, which is based on the the table design.  The size and data type of each column and est. number of rows.  Then you can est. the size of the index for the table.  You do need to include free space for a table that is updated a lot.

Once you have the size of each table and its index (including free space) then you just add them together and you have the database size.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> What r the guideliness to be followed regarding estimation etc before creating the DB.

In this case, you need to calculate the

* Estimated size of your tables.
* Estimated size of your Clustered Indexes.
* Estimated size of your Nonclustered indexes.

And few links to start out since you are new to this:

http://msdn.microsoft.com/en-us/library/ms187445%28SQL.90%29.aspx
http://msdn.microsoft.com/en-us/library/ms175991(SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms189124(SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms178085(SQL.90).aspx
http://msdn.microsoft.com/en-us/library/ms190620(SQL.90).aspx
0
 
dotnet0824Author Commented:
ok thanks. finally what is the number of  user concurrent connections to do with database size? can it be explained pls.
0
 
giltjrCommented:
Nothing.  

But you also asked about memory and processors.  These deal with performance and performance is not just related to the size, but also the transaction rate, which is typically related to number of concurrent users.
0
 
dotnet0824Author Commented:
Thanks guys..
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 5
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now