Home/ Questions/Q 828181
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T03:41:17+00:00

I have read these very good questions on SO about SQL stored procedures: When

  • 0

I have read these very good questions on SO about SQL stored procedures:

I am a beginner on integrating .NET/SQL though I have used basic SQL functionality for more than a decade in other environments. It’s time to advance with regards to organization and deployment. I am using .NET C# 3.5, Visual Studio 2008 and SQL Server 2008; though this question can be regarded as language- and database- agnostic, meaning that it could easily apply to other environments that use stored procedures and a relational database.

Given that I have an application with inline SQL queries, and I am interested in converting to stored procedures for organizational and performance purposes, what are your recommendations for doing so?

Here are some additional questions in my mind related to this subject that may help shape the answers:

  • Should I create the stored procedures in SQL using SQL Management Studio and simply re-create the database when it is installed for a client?
  • Am I better off creating all of the stored procedures in my application, inside of a database initialization method?
  • It seems logical to assume that creating stored procedures must follow the creation of tables in a new installation. My database initialization method creates new tables and inserts some default data. My plan is to create stored procedures following that step, but I am beginning to think there might be a better way to set up a database from scratch (such as in the installer of the program). Thoughts on this are appreciated.
  • I have a variety of queries throughout the application. Some queries are incredibly simple (SELECT id FROM table) and others are extremely long and complex, performing several joins and accepting approximately 80 parameters. Should I replace all queries with stored procedures, or only those that might benefit from doing so?
  • Finally, as this topic obviously requires some research and education, can you recommend an article, book, or tutorial that covers the nuances of using stored procedures instead of direct statements?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Consider skipping stored procedures for an ORM. Consider using:

    • LINQ To SQL
    • Entity Framework

    • SubSonic

    • You’ll be writing less boiler plate ListCustomer and GetCustomerByID code when you could be adding more value to your application.

    • IMO, there isn’t any real compelling reason to choose stored procedures with the modern toolset that we have in the Microsoft stack.

    • The move away from inline SQL statements is good, and an ORM will help parameterize your queries for you. You don’t have to think about it.

    • You don’t have to mess with ADO.NET objects at all. Code your data access in an object oriented fashion.

    • 0