Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have a customer that runs Axapta 3.0 with Oracle. The database is getting rather big, and we have discovered that the table PRINTJOBPAGES contains a large amount of data (several gigabytes). I know there are a relation between PRINTJOBHEADER and PRINTJOBPAGES and that they are system tables used for the print archive. But part from that I dont see much information about them in the documentation.My question is if it is possible to truncate these tables to free up data in the tablespaces? What could be the possible loss of doing so?
These tables indeed contains records for a print archive. It could possibly contain any report. Sometimes it is used to store an archive of sent invoices.
It is possible to truncate to free up some space, but first check the contents and the requirements for having these as a backup.
Thank you for the answer!
Business Applications communities