This will do it...

declare @temp table (t int)

insert into @temp

select 234000 --.65

union all

select 2052000 -- 5.7

union all

select 1638000 -- 4.55

union all

select 1620000 -- 4.5

select *, t/36000.0 ,t/36000

from @temp

WHERE t/36000<>t/36000.0

Adrienne (1/8/2008)

---

Is this what you are looking for?

declare @temp as table (t int)

insert into @temp

select 234000 --.65

union all

select 2052000 -- 5.7

union all

select 1638000 -- 4.55

union all

select 1620000 --...

July (1/8/2008)

---

I have to reach another server to copy a lot of file (100 files for 1 GB). I try with

EXEC xp_dirtree "\\machine\shrarename" but I obtain "system cannot...

SELECT Part, MAX(Date) AS Date

FROM yourtable

GROUP BY Part

...and it would be a lot faster if you used BULK INSERT or BCP...

That's not such a bad idea (ad hoc usage to solve a very specific problem)... what is a bad idea is using non-temptable names for everything that you would normally...

Heh... small world we live in, huh?

Thanks for the great feedback, Ian... especially about keeping it casual (ie. fun) and the remarks about documentation... We've actually put sime "documentation standards" into play at work. They're...

Heh... I was thinking the same thing... beating are fun especially when delivered by code...

Since it's 2k5, I wonder if you could add a schema trigger to TempDB to sweep...

Speaking of testing... if you value your production system, now would be a good time to setup a testing twin so you can do full regression testing of the SP...

Just my experience... I keep a Tally table of 11k rows... sure, it covers the usual split of a VARCHAR(8000) but I use it for much more... if you consider...

Have you taken the time to verify that you actually have the problem?

Dunno about that... but I do know that throwing indexes at tables will absolutely not help code that is written incorrectly because the code will not be able to use...

Perfect... thanks for the feedback.

Yeah, anytime you have a join on different datatypes, it must do an implicit conversion to do the join... best you can get out...

You see the need to split a parameter with more than a million characters?