Originally Posted by
geekulike
We're currently looking at various packages for our school, including SIMS.
As SIMS runs on SQL Server, which is licensed to the school separately, there seems to be little Capita can do to stop custom report development or data extracts against the SQL Server database that SIMS requires.
It's just a SQL Server database, after all.
Writing back to the SIMS SQL Server database is clearly a no-no, but why would we want to?
As there are no trial, demo, or crippleware versions of SIMS available, how do we assess the complexity of the schema to decide if it will hinder custom report development, without actually buying the product? This is a key deciding factor for us.
Business Objects and the commandreporter 'API' are not the answers we're looking for ;-)