Nope... I meant it the way I posted it... but your's works, as well.

Ya just gotta love these non-discript posts, eh?

IMHO... if he wants flat files, why bother with the expense of an RDBMS???  Store it in a FILE and maintain it with a good word processor.   And access it with Binary...

Like this...

 SELECT *

   FROM yourtable

  WHERE Dept_ID = 1

  ORDER BY Member_Name

 SELECT *

   FROM yourtable

  WHERE Dept_ID = 2

  ORDER BY Member_Name

 SELECT...

3 different SELECTs.

Absolutely agree... but lot's of folks have designated "work horse" machines where they might download raw CDR's or other info to and then point SQL Server to that box to...

That's the perfect answer... too many folks try to do AI with SQL Server.

"Greforian?"   Do you mean "Gregorian" ?  Do you have a link that explains why 732312 equals to 1/1/2006?  Might be able to pull a rabbit out of the hat if...

I'm thinking that a couple of things are missing on this post, but, you can write to the client machine if you use a UNC path AND the SQL Server...

And, xp_FileExists does not require SA privs... neither does xp_DirTree which is xp_FileExists on steroids!

Remi,

Because she is using SELECT t1.*,t2.*, every spawned row is totally unique... DISTINCT will not work in this case...

If you can delete everything in the table, why can't you add an IDENTITY column?  This isn't making any sense...

The topper is separate date/time columns... one of those not so...

What do you do with names like Juliet Anne Belle Smith Jones?

P.S.

I hope to live long enough to see what happens when the pants fall off of the SmallDateTime datatype on 2079-06-07 00:00:00.000

The rule for leap years is...

Any year evenly divisible by 4 unless it is evenly divisible by 100 in which case it must also be evenly divisible by 400 to...

Hoo boy... here we go... actually, Eric is absolutely right... there is a time when you would want to have foreign keys to another database.  Here's an example as to...