You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IvoryTower currently does all database interactions using a set of SQL Server stored procedures through a set of C# wrapper classes. Business logic is split across the wrapper classes and stored procedures.
How would switching to Entity Framework change things?
Simpler and more standard query code, but more complex business logic?
Slightly worse performance, presumably?
If you'd want to stop using those stored procedures anyway, is there a database option that would be more productive but a more radical shift? What about Cosmos or another NoSQL option for text-based data?
The text was updated successfully, but these errors were encountered:
IvoryTower currently does all database interactions using a set of SQL Server stored procedures through a set of C# wrapper classes. Business logic is split across the wrapper classes and stored procedures.
How would switching to Entity Framework change things?
If you'd want to stop using those stored procedures anyway, is there a database option that would be more productive but a more radical shift? What about Cosmos or another NoSQL option for text-based data?
The text was updated successfully, but these errors were encountered: