Showing posts with label drive. Show all posts
Showing posts with label drive. Show all posts

Friday, March 30, 2012

Need help approximating how much hard drive space I need for my DB table.


In our SQL Server database we will have a table that will be populated with about 2000 records
per day. That is2000 records per day for 5 days per week. Currently the computer we are using has about 50 gigabytes
of available hard drive space on it. We are concerned that maybe we will need a bigger hard drive,
based solely on the number of records entered into this table per day. The problem is I don't
know how to calculate how much hard drive space we need. I think I read that using varchar,
sql server 2005 really optimizes a database. Here is a typical example of data in our
database. I put dots on three lines between the first and last sample record to just
illustrate that there are many records in between.

Basically we only need 8 months of data at a time in the table and then we can purge
records older than 8 months.
Can someone help me approximate how much hard drive space I might need for 8 months of data,
given the following sample record in the database?

Sample: -->34.5 4.08 10.6 .0012


Sample Table in my DB just for illustration:

(PPsquare inch) (Diameter) (Weight gm) (coeffOfSatFriction)

34.5 4.08 10.6 .0012
.
.
.
21.7 3.54 6.22 .019

Why dont you monitor your db size. Get the size on a sunday evening and check the same information on friday evening, you will see how much your db has increased. monitor this over a couple of week and you will get a better estimate. Also, create a job that will alert you if the db size reaches 70% of allocated space.|||Well actually right now we are in design mode and no dat is in the database yet. The software to populate the tables in the database has not even be written at this point in time. Basically we are required to calculate the estimated hard drive space over an 8 month period. Then based on the approximated database size we will make a decision from there. So I need to figure out a way to calculate a good estimate of the size of that data table in the database. I don't know if SQL server does any type of data compression if necessary?|||

Hi,

The estimate depends entirely on the type of data you want to store. For an article on data types sizes, you can have a look at this article:

http://msdn2.microsoft.com/en-us/library/ms187752.aspx

Based on the sample in your post, you could use a decimal with a precision of 9 (http://msdn2.microsoft.com/en-us/library/ms187746.aspx for decimal data type) which takes 5 bytes for each field. So, your estimate would be something like this:

5 (bytes) x 4 (fields) x 2000 (records) x 5 (days) x 36(approx 36 weeks in 8 months) = 7 200 000 bytes = 6.87 Megs of data. So those 50 gigs of data would be more than enough to keep your table.Smile

|||

Thank you very much for the help!

Kind regards

Friday, March 9, 2012

Need Advice on Backups

We are a pretty small sized company that has one sql server that also
serves as our application server. We backup our server to a tape drive
nightly using Veritas. We have a Dell PowerValut 110T.
Starting about two days ago (much to my dismay) backups started
failing.
We have 3 main SQL Server databases we use for applications. They are
all in 'simple' recovery mode and full backed up once a night at 8pm
the ta a file on the server. The location which that file lives is
not backed up to tape drive.
The veritas tape backup USED TO do a FULL backup of the databases when
it runs at 9pm. nightly.
The only way I can get my tape backups to stop failing is to put the
tape backup in 'differental' mode. Which i'm not sure if is ok or
not.
I don't have the space on my tape drive to do a full backup.. That's
why the backup is failing. I have limited space on the server so i'm
not sure changing to full recover is an option. I need some help and
advice to get the best backup plan i can with what I have.
Thanks.Well!, Space , Space is all the cry around.
Need to have lots(Tons) of space, when working on Critical Database
Servers.
What is your Backup Retain Strategy on Local Server as well the TAPE.
Have Rolling Backup Plans. i.e retain backups for lesser #of days.
Take a Weekly Full Backup+Daily Differential Backup+(if possible and
space permits Transaction Log Backups every few Hours).
It Depends : How Critical is your Data!,
What is the Amount of Data Loss can you Take.(Time between one
transaction log and next)
Try 3rd Party Compression Tools - SQL LiteSpeed - Good Compression.|||This might get you through for a while. It is not an approach I would
care to use in production, but then neither is Simple recovery mode.
Monday, Thursday: A full, B differential, C differential
Tuesday. Friday: A differential, B full, C differential
Wednesday, Saturday: A differential, B differential, C full
Sunday: all differential
Roy Harvey
Beacon Falls, CT
On Thu, 01 Nov 2007 12:12:17 -0700, TDanley <taranbuckley@.hotmail.com>
wrote:
>We are a pretty small sized company that has one sql server that also
>serves as our application server. We backup our server to a tape drive
>nightly using Veritas. We have a Dell PowerValut 110T.
>Starting about two days ago (much to my dismay) backups started
>failing.
>We have 3 main SQL Server databases we use for applications. They are
>all in 'simple' recovery mode and full backed up once a night at 8pm
>the ta a file on the server. The location which that file lives is
>not backed up to tape drive.
>The veritas tape backup USED TO do a FULL backup of the databases when
>it runs at 9pm. nightly.
>The only way I can get my tape backups to stop failing is to put the
>tape backup in 'differental' mode. Which i'm not sure if is ok or
>not.
>I don't have the space on my tape drive to do a full backup.. That's
>why the backup is failing. I have limited space on the server so i'm
>not sure changing to full recover is an option. I need some help and
>advice to get the best backup plan i can with what I have.
>Thanks.