Right now I'm diving into the Umbraco database to get a better knowledge of where everything is stored. I'm using SQL Profiler to quickly see which tables are updated.
After adding some nodes/types I notice Umbraco uses different ways to get sets from the database. Mostly the stored procedure sp_executesql is used, followed by an SQL Statement. But in other cases there is just an regular SQL statement doing the call to the database. When a stored procedure is used, mostly there are a lot of parameters in the statement.
So is my guessing right that the choise between SQL or Stored Procedure depends on the parameter count? I've read somewhere that this provides better performance?
Diving into the Umbraco database: Distinction in using SQL or Stored Procedure
Right now I'm diving into the Umbraco database to get a better knowledge of where everything is stored.
I'm using SQL Profiler to quickly see which tables are updated.
After adding some nodes/types I notice Umbraco uses different ways to get sets from the database.
Mostly the stored procedure sp_executesql is used, followed by an SQL Statement.
But in other cases there is just an regular SQL statement doing the call to the database.
When a stored procedure is used, mostly there are a lot of parameters in the statement.
So is my guessing right that the choise between SQL or Stored Procedure depends on the parameter count?
I've read somewhere that this provides better performance?
is working on a reply...