Ah... got it... had to go back and look... Serqiy is correct and I'll throw in that you may not ever want to pass date serial numbers between products... Best...

Yep... accidental cross join... tell me where the join criteria is for the "sy" table alias...

 SELECT D1.stu_sid, D1.stu_id, Min(D1.Entry_Date) as Entry_Date,
     Case MAX(D2.Exit_Date)
     When '01/01/2900' then null
     Else  MAX(D2.Exit_Date) end   ...

Ummm... I gotta agree with that... tampering with server settings without knowing the full ramifications of each setting is nearly certain death for the server.  I'd get some qualified help...

It was a spoof, David...

Cool Kurt... wanna share your SQL code on this?

You really need to look at a good calendar for the year 2002...

2002-05-03 is a Friday... count 1 day

There are 4 full weeks after that up to 2005-05-31...  count...

My pleasure... thank you for the feedback.

I think you're asking for trouble by converting to decimal... but it's your data...

You can build a couple of functions from the following example...

DECLARE @IPAddress VARCHAR(15)
    SET @IPAddress = '5.152.61.94'
DECLARE...

Ummm.... you need to identify to us what makes a "duplicate" and, perhaps, post the DDL for the table where the dupes exist.  Elimination of duplicates is not difficult but...

Wow... been there and done that... Glad to see you got a got DBA for a change.

Yep... you've got it... just wanted to make sure

And, selecting more columns than you need may also cause high speed INDEX SEEKs to change to mere INDEX SCANs, not to methion the additional network traffic that selecting more...

Too bad that SET XML_SHOWPLAN ON doesn't work in SQL Server 2000, eh?

You really want to learn?  The best way to learn is to get good enough to teach.  The only way to do that is to practice.  The best way to...

First, thank you for the high compliment.

The thing that makes it "set based" is the fact that only the effect on a column was considered.  Yes, it appears that a...