DB size issues

Hi,
Our Proxy Log DB was about 50 gb so we backed it up and deleted all entries
prior to the new financial year. After backing up the smaller DB, it was
reduced in size to around 5 gb. but selecting properties from the actual
database still shows it at 50gb. Would this have something to do with unused
rows, and if so how would we be able to delete them?
Just starting out with SQL, and in need of help.
Thanks in advance2 ways
a. from enterprise manager, right click on db ->all task->shrink database
you can choose either shrink database or shrink file
b. from query analyzer, dbcc DBCC SHRINKDATABASE/ dbcc shrinkfile
--soonyu
"FIoater" wrote:

> Hi,
> Our Proxy Log DB was about 50 gb so we backed it up and deleted all entrie
s
> prior to the new financial year. After backing up the smaller DB, it was
> reduced in size to around 5 gb. but selecting properties from the actual
> database still shows it at 50gb. Would this have something to do with unus
ed
> rows, and if so how would we be able to delete them?
> Just starting out with SQL, and in need of help.
> Thanks in advance
>|||soonyu
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:F19FF44E-BA0B-4C2E-86B3-AC3C8FDA5311@.microsoft.com...[vbcol=seagreen]
>2 ways
> a. from enterprise manager, right click on db ->all task->shrink database
> you can choose either shrink database or shrink file
> b. from query analyzer, dbcc DBCC SHRINKDATABASE/ dbcc shrinkfile
> --soonyu
> "FIoater" wrote:
>|||Hi
It sounds like you need to implement some form of archiving and periodically
do this rather than waiting till it becomes a problem. As part of this you
may want to check out partitoned tables (SQL 2005) or partitioned views (SQL
2000/2005) where you can easily drop data in a partition. It may also help
speed up your searches if defined by the partitioning column (i.e. date).
John
"FIoater" wrote:

> Hi,
> Our Proxy Log DB was about 50 gb so we backed it up and deleted all entrie
s
> prior to the new financial year. After backing up the smaller DB, it was
> reduced in size to around 5 gb. but selecting properties from the actual
> database still shows it at 50gb. Would this have something to do with unus
ed
> rows, and if so how would we be able to delete them?
> Just starting out with SQL, and in need of help.
> Thanks in advance
>