| bio | website | fieldeffect.info |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 6 months |
| seen | Jan 31 at 3:51 | |
| stats | profile views | 0 |
|
Apr 23 |
awarded | Nice Question |
|
Nov 11 |
awarded | Popular Question |
|
Nov 16 |
awarded | Scholar |
|
Nov 16 |
accepted | Does “WHERE 1=1” usually have an impact on query performance? |
|
Nov 16 |
awarded | Supporter |
|
Nov 16 |
comment |
Does “WHERE 1=1” usually have an impact on query performance? +1 This has been my guess as well, but the reason I asked the question was to get a little more detail. I'm going to keep it open a little longer to see if I get any more input. |
|
Nov 16 |
comment |
Does “WHERE 1=1” usually have an impact on query performance? Just quoting from the second link: "On lines 19-29, I compose the basic SQL string. The condition WHERE 1 = 1 on line 29 is there to permit the users to call the procedure without specifying any parameters at all." |
|
Nov 16 |
comment |
Does “WHERE 1=1” usually have an impact on query performance? I'm just browsing the second article (because I'm not writing code for 2008 SP1 at the moment), but I see he is using 1 = 1 in his code. I'm already familiar with sp_executesql, but that doesn't eliminate the push to use 1=1, in and of itself. Maybe I'm missing something? |
|
Nov 16 |
awarded | Student |
|
Nov 16 |
asked | Does “WHERE 1=1” usually have an impact on query performance? |