Page tree
Skip to end of metadata
Go to start of metadata

Design Principles

  1. Core or Use Case-Specific. Each view needs to be defined as "core" (general purpose) or part of a well-defined and named use case (e.g. "early warning system"). The deployment mechanism thus would always deploy core views, while providing an optional mechanism for deploying one-or-more use-case specific views.
  2. Granular Data. Data should not be "rolled up" or aggregated. As views, calculations will be expensive. Furthermore any algorithms placed here would restrict the usefulness of the view - as the algorithm would only be useful in a small set of circumstances.
  3. DevOps Friendly Deploy. Views should be deployable using a tool that provides logging, idempotency, and can perform remote deployments (given valid database credentials).
  4. SQL Server and PostgreSQL Parity. The core views should be maintained in parallel for both database providers. It will not always (often?) be feasible to maintain parallel versions of the use-case specific views.
  5. Dimensional Modeling. Views should be created as either Dimensions or Facts (although there may be some trivial exceptions), ideally adhering more to Star Schema design than a Snowflake Schema. Roughly speaking:
    1. Facts contain measure values that can be used in calculations (count, sum, multiply, etc) - thus numeric or Boolean (as 0/1). Facts link to Dimensions for attribute data. Each Fact would be unique in some way, for example as occurring on a particular date.
    2. Dimensions contain attributes or labels for the data - thus could be strings, Dates, etc. Each Dimension row should be unique.
  6. Support Multiple Data Standards. Views should support data standards 2.2, 3.1, and 3.2 when feasible.
  7. Natural Key Usage. When the source table's natural key is a composite key, concatenate the values together to form a string surrogate key. 
  8. LastModifiedDate. Each dimension view should have a LastModifiedDate  column that selects the most recent LastModifiedDate  value from all of the source tables used by the view.
  9. Avoid Null. Cast null  values to empty strings, false, or 0 as appropriate. If a nullable field is a string, consider casting to something meaningful to an end-user, for example, "Unknown".
  10. Cast Numbers as Strings. If a value is a number in the ODS database, cast it to a string value (varchar ) unless it makes sense to use the value in a calculation. For example, a Data Analyst is unlikely to be running a sum over SchoolYear, so cast it to a string instead of leaving it as an integer. This improves the conceptual model provided to downstream users. Another example is a numeric identifier, such as EducationOrganizationId . As there are no cases where one will perform arithmetic on EducationOrganizationId , it should always be treated as a string in a SELECT statement.



All views for this component, whether Dimension, Fact, or other, will be in the analytics  schema.

All configuration tables, functions, or stored procedures will be in the analytics_config  schema.

View Names

  • View names will be descriptive of their purpose.
  • Views that belong to a use case collection should have the code name of that collection as a prefix.
  • Fact-style views must have the word "Fact" as a suffix.
  • Dimension-style views must have the word "Dim" as a suffix.
  • View names must be restricted to 63 characters or fewer, due to the name length restriction in PostgreSQL.
  • Names should be singular unless one row contains multiple of something.
  • View names should use CamelCase.


​Dimension view for studentsanalytics.StudentSchoolDim
Dimension view for schoolsanalytics.SchoolDim 
Fact a student's grades in a section, which belongs to the Early Warning System Collectionanalytics.ews_StudentSectionGradeFact 
Mapping configuration tableanalytics_config.DescriptorConstant

Coding Standards


  1. Where possible, utilize ANSI-SQL for maximum portability between SQL Server and PostgreSQL:
    1. Do not use identifier quoting — either [...]  or "..." .
    2. Prefer the COALESCE function over ISNULL  when replacing a null value with a concrete value.
  2. Joins should include the word "INNER" or "OUTER" for maximum clarity.
  3. Use comments to explain anything that might be nonintuitive. 
  4. Avoid aliasing, where possible. Aliases make the reader work harder to understand the query. However, there will be times when aliases are required, for example when needing to join twice to the same table. Very long table names can sometimes benefit from a reasonable alias as well, to keep line lengths from becoming excessive.


Formatting need not be a strict exercise — adherence to absolute precision in SQL scripts, where various tools have differing (or no) ability to help format a file, is difficult to achieve. The code reviewer should ensure that the file is readable and meets at least the spirit of the following preferences

  1. Place the CREATE statement on a line by itself.
  2. For the keywords WITH , SELECT , FROMWHERE , GROUP BY , HAVING.
    1. Each should be on a line by itself.
    2. Indent once except when part of a CTE or sub-query.
  3. Within each clause:
    1. Each column or condition should be on a line by itself.
    2. Indent twice (preferably 4 spaces rather than tab character).
    3. This includes joins.
  4. In the ON  clause for joins:
    1. Each criteria should be on a line by itself.
    2. Each criteria should have an additional indentation.
  5. Case does not matter — but should be consistent within a query.

Formatting Examples

Let's look at a poor example of query formatting:

[analytics].[UserDimension] AS

SELECT 	[Staff].[StaffUSI] as [UserKey],
		[StaffElectronicMail].ElectronicMailAddress as [UserEmail],
			from (VALUES ([Staff].[LastModifiedDate])
						-- [StaffElectronicMail] does not have a [LastModifiedDate]
				 ) as value([LastModifiedDate])
		) as [LastModifiedDate]
	FROM [edfi].[Staff]
	join [edfi].[StaffElectronicMail] ON 	[Staff].[StaffUSI] = [StaffElectronicMail].StaffUSI
	JOIN [edfi].[ElectronicMailType] ON [StaffElectronicMail].[ElectronicMailTypeId] = [ElectronicMailType].[ElectronicMailTypeId]
	WHERE [ElectronicMailType].[CodeValue] = 'Work'

Problems with this example:

  • Need to bring the create statement onto one line.
  • The SELECT keyword should be indented.
  • First column in select statement is on the same line as SELECT.
  • Mix of case in the SQL keywords (e.g., SELECT and from are inconsistent).
  • Preference to include keyword INNER on the joins.
  • Join conditions must be separated.
  • The WHERE condition should be on a line by itself.

The following shows a more readable example:

Improved Formatting
CREATE VIEW analytics.UserDimension AS

		Staff.StaffUSI as UserKey,
		StaffElectronicMail.ElectronicMailAddress as UserEmail,
			FROM (VALUES (Staff.LastModifiedDate)
						-- StaffElectronicMail does not have a LastModifiedDate
				 ) as value(LastModifiedDate)
		) as LastModifiedDate
	    Staff.StaffUSI = StaffElectronicMail.StaffUSI
	    StaffElectronicMail.ElectronicMailTypeId = ElectronicMailType.ElectronicMailTypeId
		ElectronicMailType.CodeValue = 'Work'

Adding Files to the Project

All SQL files added to the project must bed Embedded Resources instead of "regular files". In Visual Studio, many developers just copy and paste an existing file to create a new one; this will keep the necessary property value. 

To see this in Visual Studio, right-click a file in the Solution Explorer and choose Properties. Desired setting:


The Analytics Middle Tier unit test project includes tests both for the C# code and, more importantly, for the views themselves. These tests serve as full regression tests and should be modified any time a view is changed. All views should be "unit tested" with full coverage. For example, if someone comments out a left outer join condition, then a test should fail. 

For more information on the test framework, see Unit Test Framework.


  • No labels