Re: time conversion hiccup
- From: tatata9999@xxxxxxxxx
- Date: Mon, 08 Oct 2007 09:59:24 -0700
On Oct 7, 9:36 am, Erland Sommarskog <esq...@xxxxxxxxxxxxx> wrote:
(tatata9...@xxxxxxxxx) writes:
Interesting idea, Erland, but it did not seem to work for me, maybe I
didn't do it right? Only two variations.
We have only seen fragments and pieces of what you have been doing. It
would help if you posted a create table statement for your table, insert
statements with sample data, and the desired result given the sample.
That makes it easy to develop tested query. Without that, we are mainly
guessing.
--
Erland Sommarskog, SQL Server MVP, esq...@xxxxxxxxxxxxx
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Good News! Problem resolved. Culprit, 'WHEN (datediff(n,start,stop)/
60 > 0)' needs to be
WHEN (datediff(n,start,stop)/60.0 > 0)
Many thanks.
.
- Follow-Ups:
- Re: time conversion hiccup
- From: Erland Sommarskog
- Re: time conversion hiccup
- References:
- Re: time conversion hiccup
- From: tatata9999
- Re: time conversion hiccup
- From: Erland Sommarskog
- Re: time conversion hiccup
- From: tatata9999
- Re: time conversion hiccup
- From: Ed Murphy
- Re: time conversion hiccup
- From: tatata9999
- Re: time conversion hiccup
- From: Erland Sommarskog
- Re: time conversion hiccup
- From: tatata9999
- Re: time conversion hiccup
- From: Erland Sommarskog
- Re: time conversion hiccup
- Prev by Date: Re: time conversion hiccup
- Next by Date: Re: Dynamic Tables Names and Temporary Tables Options
- Previous by thread: Re: time conversion hiccup
- Next by thread: Re: time conversion hiccup
- Index(es):
Relevant Pages
|