No, sorry... in order to guarantee that the pages don't overlap or repeat, you need something to absolutely guarantee the uniqueness of each row... and it doesn't necessarily need to...

Better than that, post the raw data as it appears in the file for the first 3 systems...

Heh... let's hear it for progress... pay more, get less.  Gotta love that

Heh... I know what you mean... my Co hired me because they were an Oracle shop suddenly thrust into the world of SQL Server

me always love to write all my business logics in sp only.

I'll probably get some flack for this... bit I'm with you...

You bet, Mike... and thanks for the feedback...

Uh huh... for WHICH SYSTEM?  Unless you only have one system in the data, it is impossible to determine which system these drives are for unless you have a third...

Set @append = '>>'  -- to create a file

Set @append = '>'  -- to append a file

I'm thining the above are backwards... >> is the append symbol and > is the...

Heh, heh.... I LOVE "genius" designs... life would be so boring if everyone did things right

Unless you have a 3rd column the identifies all of the entries that belong to a given system, it can't be done.

Are you all set with this or do you still need some help?

Mind sharing the solution?

Also, using ISQL is "Death by SQL" because, compared to OSQL, it is severely deprecated.  Change the ISQL to OSQL and you'll be much better off.

It may be a permissions issue... whoever you're logged in as may not have permissions to see '\\Servar2\test\xx.bak'.  Try pasting that UNC into Windows Explorer (then hit CR, of course). ...

Thought I'd throw a different slant at this one because it's an "open ended" report with no definite constraints on how many reporting periods may be requested within the start...