You can translate the question and the replies:

Identify delta for source indexes

I'm aware - with the stored procedure 'source_change', we are able to identify changes (like field added/removed/property changes) for underlying source. I observed this does not identify changes in indexes (added/dropped) in underlying database. Please advise in case we want to identify index changes in mass. Appreciate it.
INDEX SOURCE_CHANGES()
user
23-10-2023 15:11:25 -0400
code

1 Answer

Hi, In general, `GET_SOURCE_CHANGES` stored procedure is used to detect the difference between the schema of base view and the corresponding data source. At this moment, the changes made in the indexes in the underlying database can be found using the `Source Refresh` option. For instance, if I need to see the indexes of a base view, I would follow the below steps: * Under the ‘Edit’ tab, I would click the ‘Source Refresh’ option. This shows the updated information of the indexes in the base view. Please refer the [Source Refresh](https://community.denodo.com/docs/html/browse/latest/en/platform/installation/postinstallation_tasks/enable_ssl_connections_in_the_denodo_platform_servers/enabling_https_in_the_embedded_apache_tomcat) section for more information. Also, the [GET_VIEW_INDEXES](https://community.denodo.com/docs/html/browse/latest/en/vdp/vql/stored_procedures/predefined_stored_procedures/get_view_indexes) stored procedure helps to get the details of the current indexes available in the data source. Hope this helps!
Denodo Team
24-10-2023 07:56:52 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here