(Choosing Between T-SQL and Managed Code)
From Thiru Thangarathinam over at Developer.com
"When writing stored procedures, triggers, and user-defined functions, programmers now will have to decide whether to use traditional T-SQL or a .NET language such as Visual Basic .NET or C#. The correct decision depends upon the particular situation. In some cases, you should use T-SQL; in others, you should use managed code.
T-SQL is best in situations where the code will mostly perform data access with little or no procedural logic. Managed code is best suited for CPU-intensive functions and procedures that feature complex logic, or where you want to leverage the .NET Framework's Base Class Library. Code placement is another important fact to consider. You can run both T-SQL and in-process managed code on the server. This functionality places code and data close together, and allows you to take advantage of the processing power of the server."
2 comments:
Which is used in RM3? Describe the logical and physical layers between the code and the data, please.
T-SQL...In the development structure that we're working with the closest layer to the DB is the data layer, which handles data in/data out calls. The logic layer sits on top of the data layer, if needed, and contains any logic necessary to fulfill user interaction and business rules.
Post a Comment