Hi, Still a lot of customers do use the SysDatabaseTransDelete-class to remove test data. Unfortunately many of them do this because they think, they do reset the environment into a state, where it is like "clean and new" - and then start to use such a resetted environment as a PRO environment. Since this class does not completely remove ALL transactions, it is causing data corruption and will lead to problems later on while using the environment. In addition, using this class is not a supported scenario, which is causing big problems throughout the lifecyle of the product in the end. Hence I'd suggest to completely remove that class from the standard code (and later on replace it with a working class that is removing ALL data, performing a complete and supported reset of the transactional data).