Discussion
Virtusa
US
Last activity: 6 Apr 2018 19:26 EDT
Connect-SQL Schema
Hi Team,
We have created one data table in PEGA schema and using connect-SQL i tried to connect to the table to perform Create/Delete/Update operations. In the connect SQL i did not mention any schema before table name, i called this SQL on the page where the class of this page is mapped to the table using Data base table rule. I am able to connect this table in E1 dev environment. At run time schema name will be getting from the data base table urle.
But when it moves to E2-UAT environment, it is not working. But if i hard code the schema name before the table in the connect-SQL rule it is working properly.
Could you please suggest why it is behaving differently in higher environments.
Thanks,
Chiranjeevi M
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Incessant Technologies
IN
Hi Chiranjeevi,
In my opinion Data Base table rule is an Data instance, we need to add this Data instance in product file before deployment.
As you said it is working by hard coding in E2-UAT environment that means the table is present, so consider adding this data instance in your next deployment hope it will work.
Regards,
Rakesh kumar
Virtusa
US
Hi Rakesh,
Thank you for your response.
I have verified table instance, the table instance already moved to environment. One more thing that i observed is, in this env if we don`t hard code schema name( schema.Table), in this env PRPC is looking for this table in RULE schema instead DATA schema. Please see my activity as mentioned below.
Step1: Created a page of the data class(page-new), this data class mapped to table
Step2:Given the above page as step page, called RDB-LIST
In the connectSQL- I referred the table : select * from table(instead of schema.table)
Regards,
Chiranjeevi