Hi all
We have a 50GB navision 2.60 database. After some maintenance we reduced de real used space to 10GB, so we would like to reduce the size of the database to free some disk space. Is this possible? The only thing we've been able to think about has been backing up the database and restoring it into a new one with the desired space, but that is not possible as we some corruption and cannot backup the whole database.
Anyone knows another method of reducing the size?
Thanks in advance
0
Comments
RIS Plus, LLC
The corruption happens in one table (if I remember well, it's error 1190 in module 19) that has too many rows to try to find it. The error happens when we try to analyse the database of back it up.
The thing is we made a copy of the files, and worked on this copy to delete not needed information and data, and it's here where we want to reduce the size if its possible.
RIS Plus, LLC
I think it's worth the time spent, not only to reduce your database but to fix your backup problem.
Did you search the forum for "1190" I remember it having a number of posts.
http://www.BiloBeauty.com
http://www.autismspeaks.org
TechKnowledge Content
Issue
Internal Error 1190 in module 19 occurs when performing a Navision Backup on the SQL Server Option.
Note - This message refers to lowercase letters existing in a CODE field. This cannot be done in the Navision client.
Potential Cause
It is usually caused by someone putting data into a Navision table through a SQL Server tool instead of using the Navision Client. This is very dangerous and we do not recommend it.
Resolution
1. Find the table that has the problem. This should be mentioned in the error message.
2. Identify the problem fields. You may want to start by identifying all of the CODE fields in the table and then running a SELECT query on the table in Query Analyzer to identify which fields have bad data.
3. Create a report or codeunit in Navision that will loop through the table and UPPERCASE the fields that contain the bad data.
Note - There may be more tables with the same problem.
This article was TechKnowledge Document ID: 28365
I remember talking to an implementation site regarding this problem. They had to send their database to Navision to get it fixed.
It's definately better to fix it now than later, since your database will only keep growing.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
We'll try to fix the table where we are having the problem. I know it's the best option, but it's very time consumming and it's hard to dedicate the time to it.
We are not using SQL, so we are not sure how this data corruption has got in there. If we can't find the problem, we'll end up sending the database to Navision.
Thanks again for all your help!