Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am a bit confused on what method to use when creating an application that deals with MSSQL Stored Procedures and VB.NET.
Should i study and implement the Data Access Layer along side with the Business Logic Layer? Is this approach the most efficient when needing to display data from database tables and update data also or should I be approaching this another way?
Thanks
Your question is somewhat vague, but I’ll try anyway.
Yes, your data access layer should be separate from your business logic layer. It makes your code cleaner and more maintainable.
Look into ORMs like Entity Framework for accessing your database. In some scenarios, you may not even need to write stored procedures to retrieve the data you need or perform updates.