Viewing 15 posts - 56,776 through 56,790 (of 59,086 total)
I don't have your data so not sure what else is going on... the following returns 1.3 as expected... (SQL Server Developer Edition and Enterprise Edition, sp4)
DECLARE @test-2 DECIMAL(18,4)
SET @test-2...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 7:24 pm
Because, first, you must have an envelope
Lot's of folks just aren't gonna make it to 2005 because of budget and manpower. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 7:19 pm
Heh... that coming from a person that lives on an island ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:44 pm
Yes... it does work... if you actually know something about SQL
And, the responses normally go directly to the person providing the opportunity...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:41 pm
Ok... so did that do the trick for you or what? A little feedback goes a long way around here...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:31 pm
The problem is the code highlighted in red... remove it and it will work fine.
UPDATE clean
SET clean.branchid = branches.branchid
FROM clean
INNER JOIN branches
ON clean.ppi = branches.ppi
Although the following works fine...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:30 pm
SELECT CAST(LEFT(@TestXMLTime,22) AS DATETIME) works just fine...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:24 pm
Hey Remi! My car won't start... can you tell me what's wrong with it?...
Waddaya mean you want to pop the hood? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:14 pm
Hard to tell with the criteria for the "ON" clauses missing...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:09 pm
Yep... temp tables and all that other stuff work fine on tiny tables containing 2000 or even 10000 rows... try it with a million rows...
This, of course, can be done more easily...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 4:04 pm
HOW does it save time?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 3:58 pm
You bet. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 3:44 pm
It may be a bug in TOP that someone recently reported for SS 2k5. Stupid little things like...
SELECT TOP (75) PERCENT *
FROM sometable
Yield the incorrect results... but not all the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 7:51 am
Here's a fully functional example, using the Northwind database, of how you could do it in SQL Server... most folks turn it into a function....
USE NorthWind
DECLARE @RegionToFind VARCHAR(20)
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 7:35 am
>>just add the genre to the genres variable
Are you looking for the Genres variable to contain a list of space separated Genre's? or ???
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2007 at 7:02 am
Viewing 15 posts - 56,776 through 56,790 (of 59,086 total)