R
Robert Strickland
Earlier today I was in a discussion with the team's DBA on where explicit
database transaction locks should be placed - in the .Net application or in
the stored procedures. This can up when we ran into some concurrency
problems for our web application. Is here any guidelines or standards on
where the best place is for explicit locks? We use SQL Server 2000 and 2005
only (no Oracle and MySql). However, we do have several databases that make
up the datasource for the applications. All of the T-SQL code is in stored
procedures.
Also, with the CLR now in SQL Server 2005, is there push to move business
code from the business layer directly into SQL Server?
Thanks
Bob
database transaction locks should be placed - in the .Net application or in
the stored procedures. This can up when we ran into some concurrency
problems for our web application. Is here any guidelines or standards on
where the best place is for explicit locks? We use SQL Server 2000 and 2005
only (no Oracle and MySql). However, we do have several databases that make
up the datasource for the applications. All of the T-SQL code is in stored
procedures.
Also, with the CLR now in SQL Server 2005, is there push to move business
code from the business layer directly into SQL Server?
Thanks
Bob