Let’s discuss your questions one by one in the order you asked them
OpenAccess can handle a case in which you have associations only in the conceptual model without having constraints in the database. You can use LINQ without problems with such a scenario. The only thing you need to do is define your associations with the visual designer. Even if you do not have primary keys defined on your tables, our validation framework will help you resolve the conflicts.
I also do not think you will encounter issues with the identity mechanism you have specified. As far as I understand the identity seed is not defined on the entity table but on the common table where all the identities reside. There should not be any obstacle to get the generated id and set it to an entity in another table.
Working on a separate server is fine – in most of the real-case scenarios the deployment of the database is on a dedicated server. A valid connection string is the only thing you need to get your application running. However, in order to improve performance you can benefit of the L2 caching mechanism we provide. In short, it helps you cache persistent objects in a common in-memory pool used by several threads. This way the database connections are opened more sparingly and working in-memory with cached objects is preferred.
If you have any doubts or questions feel free to contact us and we will try to respond quickly and thoroughly.
All the best,
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items