DLINQ stands for Data Language Integrated Query allows you to quickly create entity classes and relationships using your database schema. Not only that but DLINQ provides very useful methods when persisting the data into the database. You can create the relationships using the designer. The designer will write all the code for you. Finally, when you need to persist the object into the database you call few methods and DLINQ takes care of the rest. DLINQ is designed with RAD (Rapid Application Development) in mind. This makes it harder to layer the application when using DLINQ.
The DLINQ framework uses dynamic SQL to insert data into the database. This means that the SQL is generated at runtime. Off course you can use your own custom stored procedures but then it really kills the purpose of using the DLINQ framework.
My question is that do you think your DBA will allow you to fire dynamic SQL against the database? Caste your vote using the poll which can be viewed on the GridViewGuy website.