Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>DamienG works on the LinqToSql team at Microsoft and I have upvoted his answer as correct.</p> <p>That said, he likely won't advise you away from LinqToSql and I think it's very important to consider that option.</p> <p>Trying to guess the return type of a stored procedure is very difficult and LinqToSql does it as well as anyone (for SQL Server). That said, there are very compelling reasons not to use stored procedures:</p> <p><a href="http://weblogs.asp.net/fbouma/archive/2003/11/18/38178.aspx" rel="nofollow noreferrer">Stored procedures are bad, m'kay?</a></p> <p>If you must protect your tables from developers for "security reasons" (which I'm guessing is the situation you are in), it's best to do that with views instead of stored procedures.</p> <p>If you are using views, you then have a lot better options in the ORM department than LinqToSql.</p> <p>The main problem you are going to run into with LinqToSql in this regard is that what works fine for 5 stored procedures in a tiny database doesn't work fine for 50 or 500 stored procedures. You can use the O/R Designer to "override" the return type of a stored procedure, but you will have significant syncing issues when stored procedures or the tables, etc. they operate on change. Changes to stored procedures will not get reflected in the O/R Designer unless you remove the stored procedure from the O/R Designer, re-add it, and then reapply your custom override. If your project is like any normal project, the tables and stored procedures change often and this sync issue soon becomes a nightmare because it's completely manual and if you fail to do it correctly you will get very strange errors at runtime.</p> <p>I would strongly advise against continuing down the path you are on.</p>
    singulars
    1. This table or related slice is empty.
    1. POOptimizing Stored Procedures so they will be processed properly by Linq2SQL
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMichael Maddox
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI know who Damien is an I value his comments. The reason for using stored procedures as a mechanism to access our data is not something I personally have any control over. It is an architectural decision and as a result that is what we are consuming as .NET developers. My goal in asking this question is that we have decided to use LINQ2SQL as our O/R mapping tool of choice, and I would like to provide our DBA group with whatever information I can so that they can write the stored procedures in such a way as I can consume it using LINQ2SQL instead of having to use ADO.NET.
      singulars
      1. PO
      1. USMichael Mann
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload