web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

SQL Backup very LARGE (all of a sudden)

(0) ShareShare
ReportReport
Posted on by 135

Hi All,


so to move updates from my DEV Env to the TEST Env, i simply backup the SQL Database and restore in TEST. Working easy and quick.

(i have to move the .bak from one Location to another via internet/vpn tunnel)

So far the Backup file was around 120 MB , fairly small and quick to transfer.

All of a Sudden the Backup File has a whapping 3.5 GB , and i mean from last week to today. I am not talking about Modelstore, i am talking the Table Database.

This makes transfering data much harder, what happened ? Can anyone help please?

I did export the modelstore in a seperate step before hand. But this wasnt the first time i did this.

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,967 Most Valuable Professional on at

    You have to collect more information. Fist of all, connect to your DB server in SQL Server Management Studio, right click your database and choose Reports > Standard reports > Disk usage. This will give you a quick overview of what consumes space (data, unallocated space and so on). Depending on your findings, you can try other reports (such as Disk Usage by Table) and queries to find more details.

  • new_axys Profile Picture
    135 on at

    so it turns out, dbo.XREFERENCES reserves 6.9 GB (2.4 BG of Data), dbo.XREFPATHS reserves 1.4 GB (the 3.5 BG i was mentioning in the thread is already the zipped file).

    Is it possible the Developer (who is currently working on some modifications) somehow blew up those tables ?

  • Verified answer
    Martin Dráb Profile Picture
    237,967 Most Valuable Professional on at

    These tables contains cross-references between all objects (fields, method calls etc.), therefore yes, it has something to do with developers. I don't know what's the usual size of these tables (I don't have any AX 2012 on hand), but it's true that they contain a lot of records.

    On the other hand, if it's a development box, you can't just tell developers stop using cross-references. It would be like cutting off one of their hands. :) If it's not a dev box, nobody should be doing any modifications there.

    Note that indexes of xRef* tables are often horribly fragmented, which wastes disk space. If it's the case, you can get some space by defragmenting them.

  • new_axys Profile Picture
    135 on at

    Okay, thanks. That would explain the whole thing.

    Now there should be a solution to how to back up without the cross-references. i shall look that up. thanks Martin.

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    You could move those tables to a separate filegroup in SQL Server, only back up the PRIMARY filegroup and log file, to be shipped between environments.

  • Suggested answer
    guk1964 Profile Picture
    10,888 on at

    This is a very interesting thread I recommend also see this trail https://community.dynamics.com/ax/f/33/t/137796

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans