meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 3 months |
| seen | May 9 at 16:14 | |
| stats | profile views | 4 |
|
Feb 7 |
awarded | Yearling |
|
Nov 21 |
comment |
Searching for pairs of date/time values in a single row @Sam, in the 1st code bock, if the start/stop days are the same, the 2nd condition and the 3rd condition combined will return ALL rows for the day. Say the start time was 3p (150000) and the stop time was 5p (170000), the 2nd condition would return everything from 3p to 11:59:59p (150000 thru 235959) and the 3rd condition would return everything from midnight (000000 to 170000). Since the 2nd and 3rd conditions are OR'd, you get everything. That's the basic difference between the two code blocks. The 1st one is OR'd and the 2nd one is AND'd. |
|
Nov 20 |
comment |
Another BCP Export [Fail]ure @Killercam, could you use global temp tables (e.g. ##TmpTableColumnNames)? |
|
Nov 20 |
awarded | Commentator |
|
Nov 20 |
comment |
Searching for pairs of date/time values in a single row @Sam, I'm pretty sure you need both cases. I only had the second case and somebody pointed out that it will return all rows for a day if the start and stop days are the same. |
|
Nov 20 |
comment |
Searching for pairs of date/time values in a single row @ChrisAldrich, I'm not familiar with the db2 syntax. Those are supposed to be variables. |
|
Nov 20 |
revised |
Searching for pairs of date/time values in a single row added comments |
|
Nov 20 |
revised |
Searching for pairs of date/time values in a single row fixed another bug |
|
Nov 20 |
awarded | Editor |
|
Nov 20 |
revised |
Searching for pairs of date/time values in a single row fixed bug in code |
|
Nov 20 |
answered | Searching for pairs of date/time values in a single row |
|
Nov 6 |
awarded | Supporter |
|
Nov 1 |
answered | Does adding page compression to a table also compress existing indexes? |
|
Oct 19 |
comment |
Altering nullability of column in SQL Server I would guess that going from NOT NULL to NULL works because every value stored in a column defined as NOT NULL is allowed if the definition is changed to NULL. The opposite is not true. Not every value stored in a nullable column will be allowed in a non-nullable column. |
|
Oct 19 |
answered | Altering nullability of column in SQL Server |
|
Oct 11 |
awarded | Enlightened |
|
Oct 11 |
awarded | Nice Answer |
|
Oct 10 |
comment |
How do I write portable SQL that refers to a linked server? If you took this approach, I think I'd wrap the CASE statement in a function so if a server changed, I'd only have to update the function. |
|
Oct 10 |
awarded | Teacher |
|
Oct 10 |
answered | How do I write portable SQL that refers to a linked server? |
