StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POShould I switch from Web Services to Entities to do my SQL data manipulation?
primarykey
Id
3946216
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-15T21:16:36.230
FavoriteCount
0
LastActivityDate
2010-10-15T21:25:26.133
LastEditDate
LastEditorUserId
0
OwnerUserId
238260
ParentId
0
PostTypeId
1
Score
0
ViewCount
58
LastEditorDisplayName
text
Body
I have a number of web application projects in a .net environment that use web services created by my DBA to select, update, and delete data from my SQL database. My DBA suggests that he will continue to create new web service interfaces for new projects in the future. I understand that this process is somewhat inefficient in terms of performance. I think that he likes this because it gives him more control over the database, which is his responsibility, after all. I was wondering if entities would generally be a more efficient way to communicate with my SQL database. Is there anyone who is familiar enough with these two approaches to tell me which one is more appropriate to use in the future? And why?
Tags
<.net><sql><entity-framework><linq-to-entities>
Title
Should I switch from Web Services to Entities to do my SQL data manipulation?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDaniel Allen Langdon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.