BTW, you will want to do regular database backups which should keep your transaction logs at a manageable size.
Main Topics
Browse All TopicsHi,
I have an external consultant who is deploying Microsoft Navision 4.0 in our enterprise. They are having issue at the moment with the harddrive space size which is about 50GB. The problem now that i have checked online even Navision 4.0 backedn of SQL doesn't exceed more than 2GB of data in 2 year transaction of opening balance & inventory whereas on posting itself the sql database size have reached now about to 35GB where they want more space for the same.
Please advise to the same if the consultant are correct on their path or they have done mistakes on the database where it's generating such a huge size because if it's not an error i am imagning when the transactions will start where the size will reach.
Correct me if wrong.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The question was on why was the database size so large and my responses pointed to the fact that the system may have transactions logs or empty space in the data file. If the solution is:
"i did it myself by the command lines at sql & shrinked the size."
Then my answer was correct.
Additionally, I think I provided other useful information on why which was the question.
Sorry I had to, navedj786, but why would you [1] not respond to my comments; [2] delete question stating a solution that I offered without giving credit?
My recommendation would be:
Accept http:#a24999421.
Please review your own question as you asked is the consultant correct or not in requesting new space on the server and not how do I shrink the size.
Despite that I went to answer both questions as I offered you a suggestion that the size could be correct based on differences in each persons installation of an ERP system but to check your files. Re-read my comment, specifically here:
"If indeed the SQL database is 35GB by itself and you are not live yet, I would check the size of the individual files and see if the space is in the log or the data. Then check to see if actually being used. If you are in implementation phase and have been doing tons of testing, importing of data, deleting records, etc. you may have a large transaction log file and/or have a good amount of unused space within the database size."
If you were able to truncate you MDF and/or LDF file to fix the problem then what I said here was correct as you had to have had unused space. If this were not true, then you would not have gotten reduced size as truncating won't eliminate data actually in use, it will merely reclaim unused space in MDF.
Anyway, if you had responded to comment, I could have easily expounded on the how to. Just for your future knowledge, if your question is answered but you have follow-up thought or feedback, you should give the experts who responded the courtesy of a post back and a chance to aid you in the next step.
Respectfully yours,
mwvisa1
Business Accounts
Answer for Membership
by: mwvisa1Posted on 2009-08-02 at 09:56:43ID: 24999421
navedj786,
Initial note: when dealing with enterprise systems like Navision, there are probably good statistics on typical sizes and capacity specifications, but each company will probably see differences based on how they use the software and amount/frequency of transactions they have.
The size different of 35GB versus 2GB depends heavily on definitions of what is in that size and setup of system.
e.g., is the 2GB estimated strictly for the MDF (data file) for the MS SQL Server back end?
When installing MS SQL Server, you have the application binaries, the temp database, the MDF for your database, the LDF (log file) for your database, etc. that all take up space of their own.
If indeed the SQL database is 35GB by itself and you are not live yet, I would check the size of the individual files and see if the space is in the log or the data. Then check to see if actually being used. If you are in implementation phase and have been doing tons of testing, importing of data, deleting records, etc. you may have a large transaction log file and/or have a good amount of unused space within the database size.
Won't hurt to have more space though for database backups, transaction log growth, temp database usage, etc. in the future; therefore, personally, you may want to add space for production environment anyway. A good practice is to have your SQL base code on one volume/partition; data files, on another; log files; on another.
Regards,
Kevin