Skip to Content (Press Enter)
2018-10-25 14-51-08
pmmv999
47Views
6Comments
Solved
Module_PublicElement Increasing Database (OSSYS_MODULE_PUBLICELEMENT)
Question
Database
Service Center
Service Studio Version
11.53.19 (Build 61407)
Platform Version
11.13.0 (Build 31107)

Hello Everyone,

On the Client OutSystems Factory that I work on, I am performing a clean-up on the Outsystems Databases and noticed that the table "Module_PublicElement" from the Service Center is not going down.

It is exceeding the 2 GB in data and more than 3 million records.

I can understand by the name what it stores, and I did some tests on it:

  • It increases when putting some element Public Available in a Module
  • Doesn't increase by multiple Module Versions of the same Module
  • Doesn't decrease when putting that element to NOT Public Available
  • It increases when putting back the same element to Public Available
  • Doesn't decrease by deleting the element
  • Doesn't decrease by deleting the module and delete all the versions associated from the database using DBCleanerOnSteroids

Result: Doesn't decrease 
The goal is to reduce the data there, anyone already needed to do the same?

Greetings,
Pedro Vieira

0
0
07 Oct 2022
Copy Link
2018-10-25 14-51-08
pmmv999
Solution

Hi,

The discussion on this topic will continue on this Post
[DB Cleaner on Steroids] Inconsistency on Module_PublicElement (OSSYS_MODULE_PUBLICELEMENT)

Greetings,
Pedro Vieira

See solution in context
1
0
11 Oct 2022
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP

Hi Pedro,

I assume it uses soft delete, so there's an Is_Active boolean in there? So it would make sense it just grows. Also, it may be the case (but I'm just speculating) that if you first make an element non-public, but then publish the previous version of the module, that it doesn't create a new record, but just updates the inactive one?

0
0
10 Oct 2022
Copy Link
2018-10-25 14-51-08
pmmv999

Hi Kilian,


Indeed, if I publish the previous version, it won't increase this database
It is Module Version associated

I will reply to the remain statement on my next reply

Greetings,
Pedro Vieira

1
0
10 Oct 2022
Copy Link
2024-07-05 14-16-55
Daniël Kuhlmann
 
MVP

Hi Pedro,

Did you already run DB Cleaner on Steriods to cleanup soft-deleted meta-data?

Regards,

Daniel

0
0
10 Oct 2022
Copy Link
2018-10-25 14-51-08
pmmv999

Hi Daniël,

This are the steps that I have made:

1 - Create a Module with an Empty Web block Public Available

2 - Change the Web block to Not Public Available

3 - Change the Web Block again to Public Available (Total 3 Versions)

4 - Delete the Module

5 - Open DBCleanerOnSteroids and check Database Usage

6 - Go to DBCleanerOnSteroids --> Modules and run the clean on the Modules Versions

7 - Debug the DBCleanerOnSteroids Process to Check if it is going to the right path

8 - Check DBCleanerOnSteroids Database Usage again


I'm missing some step?
What exactly is, clean-up soft-deleted meta-data?

Greetings,
Pedro Vieira

0
0
10 Oct 2022
Copy Link
2018-10-25 14-51-08
pmmv999

Hi,

I did some other test where I used the 
Service Center - Factory - Modules - Check Old Module Versions to Delete

I have deleted 20 modules versions of Active Modules 

And seems that the Database Usage decreased for the pretended Database Entity

So, 
or I'm missing any step on using DBCleanerOnSteroids 
or DBCleanerOnSteroids doesn't take this Database Entity in consideration

Greetings,
Pedro Vieira

0
0
10 Oct 2022
Copy Link
2018-10-25 14-51-08
pmmv999
Solution

Hi,

The discussion on this topic will continue on this Post
[DB Cleaner on Steroids] Inconsistency on Module_PublicElement (OSSYS_MODULE_PUBLICELEMENT)

Greetings,
Pedro Vieira

1
0
11 Oct 2022
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.