Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to view Table-Valued Functions (TVFs) at the right folders in Azure Data Studio for Synapse Dedicated. #25941

Open
viswk opened this issue Sep 27, 2024 · 0 comments

Comments

@viswk
Copy link

viswk commented Sep 27, 2024

Issue Summary:
Unable to view Table-Valued Functions (TVFs) at the right folders in Azure Data Studio for Synapse Dedicated.

Known Impact: Although TVFs are supported, their absence from the Object Explorer in Azure Data Studio hampers users' ability to manage and utilize these functions effectively.

The above error existed in SSMS and it was confirmed as a Bug and later the SQL MT- SSMS Team have applied fixes on the latest version of SSMS 20.2.30 which was recently released.

Reference: Bug 3125285 SSMS does not support/show "Inline Table-values Functions" in Object Explorer for Synapse DBs, even though they are supported (visualstudio.com)

After the Fix and Latest Release of SSMS 20.2, the TVFs and Scalar functions are arranged in their respective folders even though it was created earlier.

SSMS_TVF

However, in ADS the bug/error still persists as seen below, both the scalar and TVF are aligned in same 'Scalar-Valued Function' which is incorrect.
ADS_TVF

  • Azure Data Studio Version: 1.49.1
  • OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:

  1. Connect to Synapse dedicated pool Instance through SSMS or Synapse studio
  2. Create TVF
  3. Once created check the TVF in the SSMS (on latest version) - It would be organized in right folders
  4. Now connect to Azure Data Studio to same synapse dedicated pool
  5. Check the folders -- Table Valued function folder doesn't exist at all
  6. The TVF is arranged in Scalar function folder

Does this issue occur when all extensions are disabled?: Yes/No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant