MSDE File size limitations

[bubarooni]

I have a MSDE based installation of GP's. The .mdf file is about 1.1 GB's and the .ldf file is about 700 MB's.

For puposes of the 2 GB database limitation, do I add these two files together? I've googled the topic, but have only got one result that seems relevant to what I am after. It does seem to indicate that you don't add them together.

I just don't want to walk in one day and find HR and Finance sitting around twiddling their thumbs because they can't work. I'll have some explaining to do if that happens. Would appreciate a heads up.

Thanks In Advance

 

[jymm]

I am not 100% sure, but (simplistic explanation) the mdf is the committed data and ldf is the un-committed data (not 100% true, but close enough). When regular sql truncates or compresses essentially it moves all of the data into the mdf (long story short). So in effect - I think you are at 1.8 gb. You can install the SQL tools from MS without installing SQL itself and then can see the MSDE db - when you right click on a DB and select properties the General info shows SIZE --- Then the FILES selection shows the size of the log (ldf) file and the data (mdf) file.

Good news is that you will only reach that limit when the DB tries to GROW or allocate more space, so if you can delete out any old data from GP by going to File->Mainenance->clear data (gp 9 - sry, do not remember what it was in other versions, but this should be close). You also might consider creating an archive company, copying the data from your production company to the archive (use the sql tools to help you with that one - I do this to populate our test company) then deleting old data from the production company (like maybe pre-2002 which would give you 4 active years)... just a thought.

sql 2005 EXPRESS might be a good alternative --- 4 gig 'expansion' limit and not quite as pricey as full sql 2005 (if you get above 4 gig you can afford sql 2005).

 

[VictoriaYudin]

My 2 cents: your log file (ldf) should NOT be 700MB. If it's empty, you should shrink it, if it's not, there is possibly a problem with the SQL server backups, etc. and that should be addressed. Either way, you should be able to recover most of that space and have a while longer before you run into the 2GB limit.