EF 6 and SQL Server Synonyms
Having a strange issue with SQL Server Synonyms and EF6.
EF 6 and SQL Server Synonyms
Having a strange issue with SQL Server Synonyms and EF6.
Is it possible for an entity framework core dbset/entity to provide access to non-entity columns?
In the database that I am working with, there is a table for “dynamic user-created attributes”. This table has the schema seen below …
Ef Core receives result from database before trigger is completed
In a table I have implemented a database trigger to populate a column with a calculated value (column is named ProjectCode). I use Web API controllers to create and retrieve entries from the database. An instance of my DbContext is injected into the controller.
SSD vs HDD For SQL Server
What could be causing the website to be slow, given that our production setup uses an HDD and the database size is about 60GB, especially as clients complain this issue frequently? How do we diagnose and resolve this? Will SSD be better?
Is processing data at SQL Server side better or processing at code side EF? especially for large dataset?
When I used Distinctby() the memory consumption of console app rises up to 1.5GB.
Entity Framework Reverse Engineer Only Select Schema
I have a project to try and work with an existing database we have. It’s a new project and I was going to use EF 8.0 to work with the database. I know how to scaffold from an existing database, but the DB for this project has around 100+ tables and I don’t need to deal with those tables. I only need to deal with around 20 of them for my task. And even those tables, there’s only a handful of fields that I care about. Is there a better way of setting all of this up without scaffolding a bunch of schema I don’t care about?