Viewing 15 posts - 5,881 through 5,895 (of 6,036 total)
If Cost1 is null, @ReturnValue becomes null in first statement, and all conditions will not be be true, so no further statements to execute. @ReturnValue will stay NULL till the...
November 2, 2005 at 4:16 pm
Remi, if Cost1 is NULL you function will always return NULL.
IF @Cost2 < @ReturnValue OR @ReturnValue IS NULL
will fix it.
November 2, 2005 at 3:44 pm
SET @cmdString = 'bcp "EXECUTE ' + DB_Name() + '.dbo.YourSP ''' + @Param1Value + ''', ''' + ... ''', ''' + @ParamNvalue + '' ' " queryout
November 2, 2005 at 3:00 pm
1st.
DO NOT CONVERT DATETIME TO VARCHAR!
2nd. If after serious consideration you'll decide you neet to convert to varchar,
DO NOT CONVERT DATETIME TO VARCHAR!
3rd. If anyway you must to convert it to...
November 2, 2005 at 2:51 pm
SELECT MIN(NEIGHBORHOOD_CODE)
FROM (SELECT NEIGHBORHOOD_CODE
COUNT(NEIGHBORHOOD_CODE) AS TOTAL_RECORDS,
FROM SFCVB_NEIGHBORHOODS
GROUP BY NEIGHBORHOOD_CODE)
WHERE TOTAL_RECORDS > 1
November 1, 2005 at 8:11 pm
Query system tables.
October 31, 2005 at 1:40 pm
Select t2.Date from Table2 t2
inner join Table1 t1 on t2.date between t1.DateFrom and t1.DateTo
GROUP BY t2.Date
ORDER BY t2.Date DESC
October 30, 2005 at 4:35 pm
What do you mean "precise"?
There is no such thing in math. There is only number of precise figures.
Float has 53 precise figures, decimal precision depends on it's value. 25 as...
October 28, 2005 at 4:41 am
No, it does not.
But in composite index it's better to have strongest restriction first.
In your case index (address_id, address_type) will be used much more likely then (address_type, address_id).
Of course, it...
October 28, 2005 at 1:50 am
What you are trying to store in DECIMAL(38,6) what cannot be stored in FLOAT?
Precision of FLOAT is 53 digits and size 8 bytes.
If you nees fixed comma you can covert...
October 26, 2005 at 7:23 am
And better create index on this computed column. Clustered, if possible.
Clustered index is the best option for selecting range of data.
October 26, 2005 at 7:12 am
Originally t1.Data was expected NULL in some returned rows.
But in the last query t1.Data cannot be NULL, t2.Data takes its place.
This changes direction of the join.
October 26, 2005 at 6:18 am
Author just did not follow his own logic.
On the first page he wrote:
I expect to see the following when I filter the data such that T2.Data=2 and T1.Data=5
T2.Data,T2.ID,T1.Data
2,1,5
2,2,5
2,3,NULL
And on this...
October 26, 2005 at 5:28 am
Viewing 15 posts - 5,881 through 5,895 (of 6,036 total)