When you want to create your own scripts or build your own addons for Sparx you have to analyse the API and the table structure of Sparx. Allthough the documentation of the API is really good it can sometimes help you as a developer to get an idea which tables (and entities in the API) need to be called.
It can be rather labour intensive to analyse after each modification which entities and attributes are modified since the data model of Sparx is impressive. Furthermore it is easy to forget modifying one of the entities resulting in an inconsistent repository content.
When you have a SQL-server repository the profiler in the management studio of SQL server can than be of great help. This tool shows exactly what statements are executed on the database, what the order is and which tables and columns are modified. A great help in analysing the functionality of Sparx