Home/ Questions/Q 160147
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T10:59:00+00:00

The other day I was showing a colleague some code I was working on,

  • 0

The other day I was showing a colleague some code I was working on, and in the passing he commented on the fact that I have hard coded SQL statements. Now these SQL Statements are extremely static and the ones that do tend to change I made into views on the database and have a hardcoded ‘select columns from view where ”’ kind of affair.

So my question is what is the best practice in these circumstances?

Is it to add the SQL statements as resources to the project and then call the resource in code ? Is there a better approach?

EDIT: In this case I interact with both SQL Server 2005 and Oracle Databases using .Net2.0

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

    1. Stored procedures. Prevents all sorts of possible issues with injection, maintenance. Put database code where database code belongs.

    2. ORM tool (like Hibernate, Subsonic, etc.) means you never see a line of T-SQL in the first place. Steeper learning curve, but a great practice to start sooner rather than later.

    • 0