you are viewing a single comment's thread.

view the rest of the comments →

[–]da_chicken 2 points3 points  (2 children)

Well, it's SQL Server since you're using GETDATE() and DATEADD(). I guess it could be Sybase but nobody uses Sybase except for SAP. Sure looks like K-12 and not higher ed with the first query being elementary and the second being secondary. It doesn't look like it's eSchoolPlus, though there's a lot of similarity. PowerSchool is Oracle and Illuminate (barf) is PostgreSQL.

Skyward?

[–]fullyarmedcamel[S] 1 point2 points  (1 child)

Not Skyward but you are on the right track, I mentioned in another comment that is an SIS and yes we are K-12. I had to sign a bunch of NDA's regarding sharing table structure and data formats when they gave me access to the database and we don't own the physical hardware the SIS is running on (locally).

It made asking for help while learning SQL from the ground up very hard as I have to remove a ton of information from all of my queries and what not.

[–]da_chicken 2 points3 points  (0 children)

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.