Growing SCCM DB?

Hi our SCCM db is growing bigger and bigger, right now 60 gb..
We are using SCCM 2007 R2 (SP2), running on Win 20008 R2, MS SQL 2008 R2 (SP1).
We have around 600 computers in our network.
I belive that db size is really to much for our small enviroment?
 
What could be wrong and how could I see what the problem are?
 
Update: I made a query to see the biggest tables in the DB:
 
name data_kb index_kb blob_kb  
CI_ConfigurationItems 387128 17136 2829  
LU_SoftwareList 238456 146840 4647  
CI_SDMPackages 202488 57264 6869  
CI_SDMPackageRelations 130000 32776 9495  
LU_SoftwareHash 116104 46320 124125  
StatusMessageInsStrs 110792 154155 156157  
StatusMessages 97552 37384 198199  
SoftwareInventory 92328 26336 244245  
 

It's all relative.  Most of the large tables you list are for CIs (which are software updates).  Those will almost always be the large tables in any environment.
What you could do is check your software Update Point settings; which products and classifications you are scanning for.  i.e., if you have no Vista in your environment, no need really, to sync the Vista software update rules.
Is it potentially the tempdb, that's large?  if so, check that you have (in SQL) the SIMPLE recovery model. 

Hi Sherry,
Thanks for your quick answer.
I just removed a lot of products / classifications that we dont use, hope that will help some.
Databases was set to simple recovery.
 
Here are my databases and sizes:
 
?1 073 741 824 FEPDB_xxx.mdf
3 221 225 472 FEPDW_xxx.mdf
4 194 304 master.mdf
2 359 296 MDTDB.mdf
2 359 296 model.mdf
4 456 448 MSACT.mdf
25 034 752 MSDBData.mdf
20 185 088 ReportServer.mdf
13 893 632 ReportServerTempDB.mdf
68 782 653 440 SMS_xxx.mdf
4 416 864 256 SUSDB.mdf
3 156 541 440 tempdb.mdf

If you are really worried about it, another approach would be to carefully, and very, very cautiously (i.e., take days /weeks between adjusting each setting) modify some of the tasks like "delete aged discovery data", or 'deleted aged history data"  You have to be very careful about what you change there for what means "aged" in your environment.  For some companies, change one of the tasks to daily may make perfect sense... but that's rare.  very very rare.  If you have a task that is currently "delete aged after 180 days", maybe you could change that to 120--then wait a month and see how that affects your environment. 
 
Essentially--don't go nuts in there.  You could inadvertently tell your system "delete just about every client record, because we had a long holiday weekend".  That's never any fun to recover from.  (it is recoverable...just not fun to explain to management that it'll take a week or so to get back to normal)
 
Carefully research every setting you might want to modify, and what the ramifications might be for your environment, and how you use the CM system.  Every company is different in their processes and procedures--what makes perfect sense at 1 company would be let's-work-for-days-to-recover-from-this-oops-generating at another.