I'm making my first WCF Service and I am unsure which route I should take with stored procedures and Linq to Sql. I understand that I can drag and drop stored procs to my DBML file and call them that way, or call them directly, not using the dbml. Is there a reason why i should choose one over the other? I guess I'm a little confused... Any input is greatly appreciated!
+1
A:
Well, do you already have a Linq-to-SQL data model, which you use in your WCF service? If so, I would probably put my stored procedures into that data model.
If you don't already have and use a Linq-to-SQL data model, I don't really see much use and sense in creating one just to be able to call a stored procedure.
If you don't already have a Linq-to-SQL data model, I'd probably just use the straight ADO.NET code to call that stored procedure, send in any parameters coming from the WCF service method, and passing back any data you need to send back. In that case, you'd use a SqlConnection, a SqlCommand (CommandType set to StoredProcedure), a bunch of SqlParameters, and then call the command.ExecuteNonQuery() or command.ExecuteReader() methods (depending on what your stored proc is doing).
marc_s
2010-08-05 16:21:09
I do use a Linq to SQL data model already. I just didn't know if there was any added performance/functionality/standard if I use the Linq to SQL data model.
Jisaak
2010-08-05 17:55:08
@Jisaak: no, not really - it's just easier to call the stored proc from your Linq-to-SQL data context since you don't need to deal with setting up connections and connection strings and so forth. Convenience: ++, performance: no benefit
marc_s
2010-08-05 18:47:40
Ok. Thats all I needed to know. Thanks!
Jisaak
2010-08-05 20:07:54