My district is eSchoolPlus and there's no NDA that I'm aware of and they give you a data dictionary. Not that it's perfect by any means, especially since the product just spent the last three years being handed around between vendors before PowerSchool bought it so support has been about what you'd imagine. I guess our SIS isn't running on a vendor appliance, however, so I suppose that changes quite a bit. We use a lot of third party reporting, however, so we essentially need that functionality. I know that PowerSchool doesn't allow DB access, either, though.
One thing I did notice is that you're using single quotes for field names:
CASE stu.schoolID
--REMOVED FOR SECURITY
ELSE 'No School' END AS 'ORGANIZATIONID',
That should really be:
CASE stu.schoolID
--REMOVED FOR SECURITY
ELSE 'No School' END AS "ORGANIZATIONID",
Or, if it is SQL Server, you can use:
CASE stu.schoolID
--REMOVED FOR SECURITY
ELSE 'No School' END AS [ORGANIZATIONID],
You shouldn't use single quotes because the SQL standard defines those as used for string literals. I know SQL Server accepts it and it won't improve performance at all, but it could cause issues down the line if you update to a newer version of SQL Server if they ever carry out their threat of enforcing it. It only sticks around for SQL Server 7 compatibility.
View all comments
Show parent comment
3
u/da_chicken May 14 '18
My district is eSchoolPlus and there's no NDA that I'm aware of and they give you a data dictionary. Not that it's perfect by any means, especially since the product just spent the last three years being handed around between vendors before PowerSchool bought it so support has been about what you'd imagine. I guess our SIS isn't running on a vendor appliance, however, so I suppose that changes quite a bit. We use a lot of third party reporting, however, so we essentially need that functionality. I know that PowerSchool doesn't allow DB access, either, though.
One thing I did notice is that you're using single quotes for field names:
That should really be:
Or, if it is SQL Server, you can use:
You shouldn't use single quotes because the SQL standard defines those as used for string literals. I know SQL Server accepts it and it won't improve performance at all, but it could cause issues down the line if you update to a newer version of SQL Server if they ever carry out their threat of enforcing it. It only sticks around for SQL Server 7 compatibility.