You surely can write your query without the cursor.

You can use table-valued funcions (inlined or not), and make calculations set-by-set,

not row-by-row.

Temp tables or table variables could help.

If you would describe...

You'r the man, hbtkp! I'd buy you a beer if...

I doubt it goes as many table scans as there are partitions, but you can check logical reads with profiler.

Do they match partition size or whole table size, and you...

Umar, you are welcome!

Vedran

Within the CTE, where prev_Sequence is defined, you can access any column from previous row. E.g.

prev_Adm_datetime = prev.Adm_datetime

Try to learn, not just use the solution. For example, execute inner...

Probably You could use Import Wizard (Right-click on database in Object Explorer->Tasks->Import Data), and on the page "Specify Table Copy or Query" select option "Write a query to specify the...

What are you trying to achieve, what is the logic for the rows in result ?

If you are trying to find duplicates:

select st.*

FROM SourceTbl st

JOIN

(-- find duplicate valus

select s.Col_2, s.Col_3

from...

I'm sorry you never sent a complete example. That is, script that prepares your test data.

It would really help you to get the answer more quickly.

Please read this best practices...

EXECUTE .. AT .. does not exist in SQL 2000

Try this Addin: http://www.sqlxdetails.com

it does work with different db's on the same server (and the current db of course), but not (yet) over db link.

This example with procedure...

In even longer example, You should achieve these groups:

(id, Sequence, SequenceNum, GroupId)

1 First 1 1

2 Final 3 1

3 Middle 2 3

4 ...

After your explanation I understand that you want to allow updates that are within the same transaction as INSERT command.

You could read unique transaction id and in INSERT procedure store...

Use proper datatypes. Store date in date (not in varchar), int in int, etc.

If you already have it wrong (dates in varchar field), why do you try to convert them...

"The last update should not succeed" - why?

In your example there is no update that would not succeed.

And there is no command that inserts "ABCD".

First INSERT sets "A", then UPDATE...

Your procedure design is completely flawed. Do not build large "UNION ALL", but instead put required data into (temp) tables,

and then use one simple INSERT command that joins your prepared...