Stored Procedures were recently added to the Snowflake platforms. Aqua Data Studio needs to support stored procedure objects.
ADS areas that need to change:
196 KB
105 KB
106 KB
106 KB
116 KB
137 KB
Dependencies Node in Snowflake
Hi @Asif/ @Tom
We are implementing the Procedure Dependency in Snowflake.
As per implementation of other database servers there is reference/dependency information in information_schema for all objects i.e. table, view, procedures, etc.
MySQL:
DB2:
PostgreSql:
In the case of Snowflake there is no such information and the available API call “GET_OBJECT_REFERENCES” is only for tables and views.
The other possible solution is the perform string function on the procedure definition to get information about the references and dependency for a procedure.
Please let us know your thoughts on this. Should we hide the dependency tab totally or should we use a string manipulation approach?
Thanks
Hi Shrey,
Lets hide the dependency tab since we also don't have it for other objects.
Thanks,
Tom
Hi Shrey,
Lets hide the dependency tab since we also don't have it for other objects.
Thanks,
Tom
Alter Procedure
Hi @Asif/ @Tom
We are implementing the Alter Procedure Script in Snowflake.
For other database servers the Alter Script is done in two possible ways: 1. Adding Alter comment before the Procedure Definition i.e. same command as create procedure.2. Providing all possible options for Alter Procedure
In the case of Snowflake, Alter Procedure provides the following possible scripting options:
Please let us know your thoughts on this. Should we hide the script alter option for snowflake or which give all possible options to the user to alter which are available to us in snowflake?
Thanks
Alter Procedure
Hi @Asif/ @Tom
We are implementing the Alter Procedure Script in Snowflake.
For other database servers the Alter Script is done in two possible ways: 1. Adding Alter comment before the Procedure Definition i.e. same command as create procedure.2. Providing all possible options for Alter Procedure
In the case of Snowflake, Alter Procedure provides the following possible scripting options:
Please let us know your thoughts on this. Should we hide the script alter option for snowflake or which give all possible options to the user to alter which are available to us in snowflake?
Thanks
Hi Shrey,
Since those are the only options, let's use the #2 option and provide all options.
Thanks,
Tom
Hi Shrey,
Since those are the only options, let's use the #2 option and provide all options.
Thanks,
Tom
I agree with Tom. Show all the options.
Thanks
Asif
I agree with Tom. Show all the options.
Thanks
Asif
Revision #58506
Committed by krishna.agarwal Today 14:07
Overall changes look OK. Can you address the following:
-- public final class ExtractParameter
AFParameter aParameter = new AFParameter(param.substring(0, param.indexOf(" ")).trim()); aParameter._dataType = param.substring(param.indexOf(" ") + 1).trim();
Thanks
Asif
Revision #58506
Committed by krishna.agarwal Today 14:07
Overall changes look OK. Can you address the following:
-- public final class ExtractParameter
AFParameter aParameter = new AFParameter(param.substring(0, param.indexOf(" ")).trim()); aParameter._dataType = param.substring(param.indexOf(" ") + 1).trim();
Thanks
Asif
Hi Tom/Asif,
we have created stored procedure with optional parameters like strict/execute as owner, after the procedure is created those optional parameters are not shown in properties window or either in preview SQL tab. Because of this when we generate schema script of the procedure optional parameters are not being included. Is this expected?
procedure we used
Hi Tom/Asif,
we have created stored procedure with optional parameters like strict/execute as owner, after the procedure is created those optional parameters are not shown in properties window or either in preview SQL tab. Because of this when we generate schema script of the procedure optional parameters are not being included. Is this expected?
procedure we used
Hi Mounika,
You are correct. All parameters in the create statement should be available in scripting assuming they can be extracted.
Hi Vaibhav,
Please have a look at this and if the parameters are available from the extract, please include them in the scripting.
Thanks,
Tom
Hi Mounika,
You are correct. All parameters in the create statement should be available in scripting assuming they can be extracted.
Hi Vaibhav,
Please have a look at this and if the parameters are available from the extract, please include them in the scripting.
Thanks,
Tom
Revision #58534
As per Mounika's comment the optional variables are now visible in scripting options for Snowflake.
Revision #58534
As per Mounika's comment the optional variables are now visible in scripting options for Snowflake.
Hi Vaibhav,
I don't think the F5:Detail window is working correctly when I select parameters in Snowflake. See here, It should probably behave similar to DB2. Please have a look.
For some reason, not all sp's are getting previewed using script generator. See here and here.
We can get rid of Create Procedure in Editor for Snowflake...
Thanks,
Tom
Hi Vaibhav,
I don't think the F5:Detail window is working correctly when I select parameters in Snowflake. See here, It should probably behave similar to DB2. Please have a look.
For some reason, not all sp's are getting previewed using script generator. See here and here.
We can get rid of Create Procedure in Editor for Snowflake...
Thanks,
Tom
Hi Shrey,
Name and data type are fine for the detail window.
The Script Object as Revoke to the QA window doesn't seem to be working. Please have a look at that.
Thanks,
Tom
Hi Shrey,
Name and data type are fine for the detail window.
The Script Object as Revoke to the QA window doesn't seem to be working. Please have a look at that.
Thanks,
Tom
Hi Tom,
The specified changes are made in the revision #58588
Thanks
Hi Tom,
The specified changes are made in the revision #58588
Thanks
Verified on build Aqua Data Studio 22.0.0-dev-26-no-ofsc Build #: 58607
Windows 10
testrail link:https://idera.testrail.net/index.php?/runs/view/4167&group_by=cases:section_id&group_order=asc&group_id=28023
Verified on build Aqua Data Studio 22.0.0-dev-26-no-ofsc Build #: 58607
Windows 10
testrail link:https://idera.testrail.net/index.php?/runs/view/4167&group_by=cases:section_id&group_order=asc&group_id=28023
Verified on build Aqua Data Studio 22.0.0-dev-26-no-ofsc .
platform : Mac catalina (10.15)
testrail link:
https://idera.testrail.net/index.php?/runs/view/4168&group_by=cases:section_id&group_order=asc&group_id=28023
Verified on build Aqua Data Studio 22.0.0-dev-26-no-ofsc .
platform : Mac catalina (10.15)
testrail link:
https://idera.testrail.net/index.php?/runs/view/4168&group_by=cases:section_id&group_order=asc&group_id=28023
QA Verified:Snowflake schema tree does not show Procedures.
On build Aqua Data Studio 22.0.0-dev-26-no-ofsc and its working as expected.
platform : Ubuntu
testrail link: ADS 22.0 test suite - Ubuntu - TestRail
QA Verified:Snowflake schema tree does not show Procedures.
On build Aqua Data Studio 22.0.0-dev-26-no-ofsc and its working as expected.
platform : Ubuntu
testrail link: ADS 22.0 test suite - Ubuntu - TestRail
Moving to automation team for further action on this
Moving to automation team for further action on this
Automation verified. Please find the test run below.
https://idera.testrail.net/index.php?/runs/view/4381
Automation verified. Please find the test run below.
https://idera.testrail.net/index.php?/runs/view/4381
Issue #15799 |
Verified |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build dev-24 |
No time estimate |
Dependencies Node in Snowflake
Hi @Asif/ @Tom
We are implementing the Procedure Dependency in Snowflake.
As per implementation of other database servers there is reference/dependency information in information_schema for all objects i.e. table, view, procedures, etc.
MySQL:
DB2:
PostgreSql:
In the case of Snowflake there is no such information and the available API call “GET_OBJECT_REFERENCES” is only for tables and views.
The other possible solution is the perform string function on the procedure definition to get information about the references and dependency for a procedure.
Please let us know your thoughts on this. Should we hide the dependency tab totally or should we use a string manipulation approach?
Thanks