LINQ to SQL and Entity Framework don’t support the geometry data type… boo…

Today I had a conversation with a co-worker that started with my declaration of not wanting to ever have to code a stored procedure. Adamantly I know that there are places where sprocs are the solution to a problem but in today’s landscape I feel those are edge cases. Our argument..err..I mean conversation had all the usual discussion points. co-worker points: sprocs are faster sprocs are more secure sprocs provide a layer in n-tier My points: the dollar cost of milliseconds of speed true see comments; but all queries should be parameterized hence not a valid argument. an unnecessary abstraction...

LINQ requires all tables that you work with to have a PK. If you don’t have a PK on a table you can use the designer to set a PK on the generated code. This won’t effect your database. In Visual Studio open the LINQ Designer. Select a row you would like as your PK and select properties. Update the “Primary Key” Property.