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 take advantage of user-defined temp schema emulation in SQL server dialect #380

Open
jgholap opened this issue Nov 11, 2024 · 0 comments

Comments

@jgholap
Copy link

jgholap commented Nov 11, 2024

Hello,

I posted this in Atlas repo and got redirected to this repo. Reference: OHDSI/Atlas#2973
We are using Azure Synapse (SQL server dialect) for CDM and have been able to stand up Atlas. It uses temporary tables in the SQL generated for cohorts and other parts of Atlas. We are trying to setup temp schema so that it can store temporary tables in temp schema like its supported for most other data systems (oracle, impala, spark etc.). It looks like we have that solution already for other databases but OHDSI ecosystem just defaults to using traditional temporary tables (that start with # in name) for Microsoft based SQL Server flavors (SQL server, Azure Synapse etc.)
There are also new Microsoft data platforms in Fabric (Synapse Warehouse ) that will likely support existing SQL server dialect but due to change in architecture they may not support temp tables , so i think it would be nice to be able to store temporary tables in user-defined temp schema as it can be implemented in these products.
Having that said, can we consider it as an enhancement to improve the ability of customizations related to temporary tables ?

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