Whenever possible, you should avoid putting 'functions' in the 'WHERE' clause. Things like 'convert', 'datediff', 'upper', etc.

It isn't a problem for small datasets, but can be for large datasets....

Have you looked at what this returns...

select getdate()

select getutcdate()

select getdate() - getutcdate()

Execute that in Query...

Geeeshhh...stop whining already...

This was a fun question that made you think and do some research.

Don't make more out of it than that. If missing the question ruined your day,...

Very good point...

This is why many people use...

where somedate >= '04/01/2008' --target date

and somedate < '04/02/2008' --target date + 1

to get all records that...

OK, I'm feeling stupid here...

I knew the script 'select' was there, but for some dumb reason, I have been scripting the 'create' lately. Its as if I totally forgot...

If I need a 'select' that has a lot of columns, I'll script out the source table 'create', then manually edit out the extra stuff.

Deleting the extra is...

I don't believe you need to add the time when setting your start_date, as that is implied...

'24/07/2007 00:00:00' = '24/07/2007' (when datatyped as datetime)

The...

Does the datetime field in the database have a time component? Or is the time 00:00.

If the time is not 00:00, you won't get a match.

[Edit: it won't...

If you are not getting an error and just getting no records, check that...

I run a query in...

Since no version specified, I thought that wasn't an issue...WRONG!

This was a good exercise as it pointed out something that wasn't obvious.

I'm working on SQL 2000 right now...

Steve, I really enjoy reading your editorials about non-computer subjects and hearing about life on the farm and other things like your Prius update.

I live in a banking...

I'm not 100% positive, but I think SET ANSI_WARNINGS ON can go INSIDE the stored procedure (after the CREATE), so that when the SP runs, it sets ANSI_WARNINGS ON for...

AVB (3/25/2008)

SET @LineItemBody = '"LI' +'","'+ --Record ID

.....

IF isnull(@LineItembody,'') = '' --Line Item Body will be null if an Order Number doesn't have any rows in the transaction tables...

You can still use the stored procs to return the data, I was saying build a function to parse out a comma-delimited string, such as containing multiple Order Numbers.

For...