I know that those 3 criteria define set-based operation.

There is nothing about ordering in there.

And I see that Jeff's solution fits those criteria.

So, it's set-based, if it does use ordering...

Matt,

the nature of the task requires some kind of ranking for the rows.

So, order MUST be present in any query performing this task.

Why Jeff's method is set based?

Because:

- it opens...

You know, I use to have on my local test server Ukrainian collation and German language as default settings.

Just to make all locale dependant things like DATENAME(dw, StartDate) = 'Sunday'...

Matt,

Who told you that subquery is "set based"?

If you heard it from a person don't listen to his/her judgements anymore.

If you read it in a book - throw it away.

Cause...

> one that has some useful info

Which will not be read by anybody.

Did you notice how quickly they all lose interest when it comes to something what does not fit...

Noel, check BOL.

"\n" means different things when used in BULK INSERT statement and in Format File.

And only interpretation of Format File works for UNIX files.

Cees,

stop messing with direct declarations.

It's not gonna work.

You gonna need to create format file anyway. No matter how hard you'll try to avoid this.

Yes, it's painful task, but without...

Cees, you need to use format file.

The way you did it you specified rowterminator as CR+LF - Windows "End of Line".

Unix files use only LF to end lines.

That's why for...

You know, it's actually not a big problem if his SQL skills were not so good when you hired him.

Problem is that after a year working with you as a...

But brings something to talk about!

It's a bad idea to use Hungarian notation for objects in database at all.

Hungarian notation is good for compilers, but T-SQL is interpreter.

It just inflates system indexes, slows interpreting of...

Try to copy 9 gig file from one folder to another.

How long does it take?

And it's simplest thing you can do to 9 gigs.

Tempdb does not store any permanent data....

Set up a trigger on source table to record (in separate table) PK values affected by INSERT/UPDATE/DELETE statements performed on that table.

Then you need just join to this trace table...

Search this forum for "split function".

Choose one of them and use like this:

Select *

from MyTable MT

INNER JOIN dbo.ChosenSplitFunction (@Ticker) V ON MT.Code = V.Value

select @sql = 'bcp ORLANDO..vwEmpReport out

c:\bcp\report.csv -c -t, -T -S'+ @@servername