Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Is my db too full

Author  Topic 

Hommer
Aged Yak Warrior

808 Posts

Posted - 2007-03-28 : 13:55:14
Hi, All,
Is my db too full? If it is, what should we do? Will auto growth take care its expension?

Users report slow response time.

After checking into it, here are the numbers:

MDF file size 16G located on SAN drive with 20G, 4G free space. 85% Full. It is set to auto grow 500MG with unlimited max space.

LDF size 500 MG, with 13 G free in another SAN drive. It is set to auto grow 10% with unlimited max space.

This is a sql2000 std with sp3.

How to add more space to for the MDF file? My network admin said the SAN space allocated to it is big enough. What do you think?

Thanks!

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-03-28 : 14:06:47
We don't add disk space until we are over 90%.

Do you know how fast your database is growing? Are you able to approximately tell the network admin when you'll need more space?

How much free space do you have in the MDF file?

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

Hommer
Aged Yak Warrior

808 Posts

Posted - 2007-03-28 : 14:23:06
Space allocated (MB) is 16405 currently under db property data files tab.

Can I just change that to 17405 in live mode without any negative impact on the server?

I think its growth rate is about 1g for every two months.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-03-28 : 14:27:47
Well you don't need to do that as you are set to auto grow. But you can run ALTER DATABASE to expand the files manually. I am not sure if it will impact anyone when it's expanding, so I would do it during a maintenance window or late at night.

Tara Kizer
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

rlaubert
Yak Posting Veteran

96 Posts

Posted - 2007-03-28 : 15:55:38
Problem is not the size of the database. SQL will easily handle terabytes for database size. I would look at indexes, stats, fragmenation. When was the last time you updated the stats on the server? How about index fragmentation? When the users indicate it is too slow, can YOU prove it is or is not? Have you been creating stats on performance? Do you have a base line of CPU, Drive, Memory, Connections, etc. If so, how is it different from your baseline. Next we have a great tool in SQL for figuring out what is happening called Profiler. You can use it to determine what queries are running, what resources they are taking up, how long they are running. Also the execution plans, have they changed? You may find that SQL is no longer using an index and doing tablescans instead.
Just a few things to look at :)

Raymond Laubert
MCDBA, MCITP:Administration, MCT
Go to Top of Page

Hommer
Aged Yak Warrior

808 Posts

Posted - 2007-03-29 : 10:04:36
Thanks to both of you!

I am doing an audit right now and will compare the result to the benchmark/baseline.

Go to Top of Page
   

- Advertisement -