![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
http://msdn.microsoft.com/en-us/libr...SQL.90%29.aspx describes the PARAMETERIZATION FORCED option for SQL Server 2005 databases. I don't see how to tell whether PARAMETERIZATION FORCED is in effect on an existing database. What am I missing? |
|
Evidently it's better if an application programmer uses queries with parameters defined appropriately in the first place, but since I don't own a gun (not yet) I can't enforce that. |
#3
| |||
| |||
|
|
Robert Carnegie (rja.carne... (AT) excite (DOT) com) writes: http://msdn.microsoft.com/en-us/libr...SQL.90%29.aspx describes the PARAMETERIZATION FORCED option for SQL Server 2005 databases. I don't see how to tell whether PARAMETERIZATION FORCED is in effect on an existing database. *What am I missing? SELECT name FROM sys.databases WHERE is_parameterization_forced = 1 |
|
Evidently it's better if an application programmer uses queries with parameters defined appropriately in the first place, but since I don't own a gun (not yet) I can't enforce that. Actually, I see no reason why you (or your manager) should not accept that developers are not doing their job. And a developer that is inline parameters is definitely not fulfilling his duties in my opinion. |
![]() |
| Thread Tools | |
| Display Modes | |
| |