Oracle PowerSchool SIS - Standards View

[jfrancoalzate]

Hello PowerSchool Team and Community Members,

I am currently working on replicating several PowerSchool database views within a Snowflake environment, where we maintain a synchronized copy of the PowerSchool tables. One of the views I need to reproduce is the Standards view.

Unfortunately, I do not have the necessary privileges to view the CREATE VIEW definition directly through Oracle SQL Developer. To ensure accuracy in recreating this view within Snowflake, I’m seeking the SQL definition (DDL) or documentation that outlines the tables, joins, and filters used in constructing the STANDARDS view.

If anyone with appropriate access could share the SQL definition or provide insight into the main data sources and logic behind this view, it would be greatly appreciated.

Thank you very much for your time and assistance.

Kind regards,

Julian Franco
Senior Developer
Cherry Creek School District

[matte236]

---

@jfrancoalzate wrote:

Hello PowerSchool Team and Community Members,

I am currently working on replicating several PowerSchool database views within a Snowflake environment, where we maintain a synchronized copy of the PowerSchool tables. One of the views I need to reproduce is the Standards view.

Unfortunately, I do not have the necessary privileges to view the CREATE VIEW definition directly through Oracle SQL Developer. To ensure accuracy in recreating this view within Snowflake, I’m seeking the SQL definition (DDL) or documentation that outlines the tables, joins, and filters used in constructing the STANDARDS view.

If anyone with appropriate access could share the SQL definition or provide insight into the main data sources and logic behind this view, it would be greatly appreciated.

Thank you very much for your time and assistance.

Kind regards,

Julian Franco
Senior Developer
Cherry Creek School District

---

Replicating the proprietary PowerSchool `STANDARDS` view in Snowflake requires joining the core data sources, primarily the **`STANDARDS`** table itself, which holds the standard's **unique ID**, **code**, **description**, and **parent-child hierarchy (`STANDARDSID`)**. While the exact DDL is confidential, you can accurately recreate the view by selecting the essential fields (`ID`, `CODE`, `NAME`, `STANDARDSID`) directly from the `STANDARDS` table and applying a critical filter to ensure only **active standards** are included (typically `WHERE INACTIVE IS NULL OR INACTIVE = 0`).