This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 1%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESU%3C/text%3E%3C/svg%3E)
I'm looking for some guidance on our MS Dynamics Nav 2018 database growing out of control and what we could adjust to help reduce size.
Our DB size is 179282 MB comprised of
our .mdf PRIMARY file size 399961.6 MB, of this 1782.437500 MB is Free Space
our .ldf log file size 38254.016 MB, of this 36821.468750 MB is Free Space
our .ndf Data Filegroup_1 file size 105369.6 MB, of this 335.500 MB is Free Space
we are on WS2012R2
we are on Microsoft SQL Server Management Studio 13.0.15900.1
Microsoft Analysis Services Client Tools 13.0.1700.281
Microsoft Data Access Components (MDAC) 6.3.9600.20665
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.11.9600.20671
Microsoft .NET Framework 4.0.30319.42000
Operating System 6.3.9600
We are on Version US Dynamics NAV 11.0
11.0.22292.0
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Dynamics NAV is not currently supported here on Q&A. The product group for Dynamics actively monitors questions over at
https://community.dynamics.com/nav
--please don't forget to upvote and Accept as answer if the reply is helpful--
DSPatrick might be correct, but your main problem - as far as I understood - is SQL Server related...
I don't know much about Dynamics, but I know a little about SQL Server...
So you are asking how to reduce the size of your database... as SQL Server - spoken in easy words - is just a data sink where you can store and read that data... nothing else than storage.
The magic happens in your application, and your application uses this data to provide more (business) information.
This said, the growth of your database is initiated by your application, as your business wants to have more information for decision-making, which needs even more data to provide more accurate information... so your application is the problem...
Maybe your app team has enabled additional features/feature sets, created their functionality that needs even more data, or is doing crazy stuff with existing data...
Ask them if they changed any configurations or features to store more data...
From a DBA perspective... your database is not that big, and I don't see any problems based on storage (unless your storage subsystem can provide more storage)
If you are doing any HouseKeeping like Index or Statistics maintenance regularly... everything should work as designed.
I can't see any problems based on those numbers you posted that your database is growing into crazy high values... ;-)
If your problem is more related to the application, please ask in the dynamics user forum or write down some more details on your database problem and what you are looking for.