No, no memory pressures at all.

I've requested a dbcc memorystatus (and the @@version, just to be sure)

Yes, 64-bit, sorry.

I realize the OS needs some memory and that the MAX memory should be set.

I still don't see what is keeping SQL from going over 4GB - just...

That did it!!! Thank you so much!

😀

With the scenario I have, I'm still getting an extra unwanted row.

-------------------------------------

drop table main

create table main(

col1 char(10),

col2 varchar(100))

INSERT INTO main VALUES('101','shshsfhgs')

INSERT INTO main VALUES('102','ertqehwrgs')

INSERT INTO main VALUES('0102','witpipqcqp')

INSERT INTO main VALUES('0103','retrtyhwqpp')

drop...

Thanks! I'm getting closer, but not sure if i'm there yet.

Here's a good example of what I'm dealing with:

-------------------------------------------------

drop table main

create table main(

col1 char(10),

col2 varchar(100))

INSERT INTO main VALUES('101','shshsfhgs')

INSERT INTO...

Here's a great link: http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx

I know there may not be any set rules for SQL Server choosing which process to kill in a deadlock situation, but I have seen this behavior from SQL Server...

It's possible that the job is locking up with another process. As an interactive job (when you manually run it), it would take priority. But as a scheduled...