Denodo community Q&A RSS feed Latest Denodo community questions Migrating from SSIS to Denodo Hi Team, Please note that i am part of Denodo migration from SSIS. Kindly need some support on create a denodo package based on SSIS package. I am starting my new package in production, need some assistance. Tue, 23 Apr 2024 07:18:46 GMT 2024-04-23T07:18:46Z Unable to establish connection : IO Error: The Network Adapter could not establish the connection hi team (Unable to establish connection: IO Error: The Network Adapter could not establish the connection)it shows the previous error when trying to test connection in the training database it is not loading the data from oracle,the database url is jdbc:oracle:thin:@data-server:1521:xe which is a correct format Mon, 22 Apr 2024 23:27:08 GMT 2024-04-22T23:27:08Z Denodo server is not starting Hi team I am unable to start most of the servers it says stopped when i start it(Data catalog and web tool servers) ,how can i fix this issue? Mon, 22 Apr 2024 10:28:15 GMT 2024-04-22T10:28:15Z Check for other data sources type Hello, This is very interesting but unfortunately it doesn't cover all Denodo data sources types. Would it be possible to check other sources such as: JSON WS XML CUSTOM (this includes Excel data sources). DF (delimited files) WWW Mon, 22 Apr 2024 10:01:39 GMT 2024-04-22T10:01:39Z Denodo Solution manager roles Hi Denodo experts, Scenario below: In the Denodo Dev and Stage environments we have a developer called db_1_admin who is an admin on a specific Denodo db called db_1. In the Solution manager, we have provided the stage promotion admin role. Because of this , the db_1_admin user is able to deploy VQL to the Stage environment to any database. That means, if the CONNECT DB db_1 command is missing from the VQL, then the solman automatically executes the VQL on the 1st available db in Stage , which this user should not have access to. Is there any role in Sol man that will allow a user to deploy only to their own dbs and not to other Denodo Dbs? Thanks. Sat, 20 Apr 2024 03:41:19 GMT 2024-04-20T03:41:19Z Hiding columns that users cannot execute I have implemented column level security on a view. As expected when the restricted uers executes select * from the view they get an error message that says that they do not have privileges on certain columns. However, the user can see the columns that they do not have access to. Is there a way to prevent the user from seeing the columns that they do not have access to? Fri, 19 Apr 2024 16:24:35 GMT 2024-04-19T16:24:35Z Returning a Select Statement in a VQL Stored Procedure Hi everyone. Simple question here. I want to create a VQL Stored Procedure that returns a Select Statement, how do I do it? I have searched through the Denodo documentation for this but haven't found any reference about it. Thanks in advance Fri, 19 Apr 2024 16:01:32 GMT 2024-04-19T16:01:32Z Vdp-queries log generation Hello Team, We are aware that Denodo logs are produced in two directories: DENODO_HOME/logs/vdp and DENODO_HOME/tools/monitor/denodo-monitor/logs (when Denodo Monitor is running). The file "vdp-queries.log" exists in both locations mentioned above. However, vdp-requests.log is only generated in the Denodo Monitor directory and not in DENODO_HOME/logs/vdp. Please advise on in which case entries are generated in DENODO_HOME/logs/vdp/vdp-queries.log as well. Additionally, could you confirm if there is a log4j2.xml file for logs in DENODO_HOME/tools/monitor/denodo-monitor/logs? Fri, 19 Apr 2024 09:18:03 GMT 2024-04-19T09:18:03Z VQL STORED PROCEDURE/INTERFACE VIEW Hi everyone, this is the SP that creates the view interface and it's intended to be created in the indicated database specified in the parameter. How can I do that? [quarta-feira 17:22] Diogo Goncalves - Passio Consulting CREATE OR REPLACE PROCEDURE create_interface_view ( vdb_name IN VARCHAR, derived_view_name IN VARCHAR, interface_name IN VARCHAR, prt OUT VARCHAR ) AS ( vdb VARCHAR; d_name VARCHAR; i_name VARCHAR; frst VARCHAR; decimals VARCHAR; radix VARCHAR; size VARCHAR; remarks VARCHAR; code VARCHAR; result VARCHAR; max_rows INTEGER; max_linha INTEGER; rown INTEGER; vql_inter VARCHAR; prt VARCHAR; CURSOR get_max_rows IS 'SELECT COUNT(*) FROM GET_VIEW_COLUMNS() WHERE input_database_name = :vdb AND input_view_name = :d_name'; CURSOR get_data IS 'SELECT CONCAT(column_name, '':'', column_vdp_type), column_decimals, column_radix, column_size, column_remarks, column_sql_type_code FROM GET_VIEW_COLUMNS() WHERE input_database_name = :vdb AND input_view_name = :d_name'; ) BEGIN vdb := vdb_name; d_name := derived_view_name; i_name := interface_name; max_linha := 1; vql_inter := '('; OPEN get_max_rows PARAMETERS (vdb, d_name) VALUES (vdb_name, derived_view_name); FETCH get_max_rows INTO max_rows; CLOSE get_max_rows; RETURN ROW (prt) VALUES (max_rows); OPEN get_data PARAMETERS (vdb, d_name) VALUES (vdb_name, derived_view_name); LOOP FETCH get_data INTO frst, decimals, radix, size, remarks, code; result := CONCAT(frst, ' (sourcetypedecimals = ''', decimals, ''', sourcetyperadix = ''', radix, ''', sourcetypesize = ''', size, ''', description = ''', remarks, ''', sourcetypeid = ''', code, ''')'); IF max_linha < max_rows THEN vql_inter := CONCAT(vql_inter, result, ','); ELSE vql_inter := CONCAT(vql_inter, result, ')'); END IF; max_linha := max_linha + 1; EXIT WHEN max_linha > max_rows; END LOOP; CLOSE get_data; vql_inter := CONCAT(interface_name, ' ', vql_inter, ' SET IMPLEMENTATION ', derived_view_name, ' FOLDER = ''/03 - business entities'''); RETURN ROW (prt) VALUES (vql_inter); EXECUTE 'CREATE OR REPLACE INTERFACE VIEW :param' PARAMETERS (param) VALUES(vql_inter); END Fri, 19 Apr 2024 08:53:31 GMT 2024-04-19T08:53:31Z LEAD function doesn't work in Denodo 8 Hi there, when I tried to use LEAD function in Denodo 8, the color doesn't change and the error shows the Function LEAD is not executable. From the documentation, the LEAD function is available in Denodo. What I have missed? Thank you! Wed, 17 Apr 2024 21:02:14 GMT 2024-04-17T21:02:14Z