Owe, my head hurst.

Can you give us an example of what you mean?

You could do soemthing liek so.

DECLARE @rowcnt int

SET @rowcnt = 1

SET ROWCOUNT 1000

WHILE @rowcnt > 0

BEGIN

--UPDATE STATEMENT HERE

SET @rowcnt = @@ROWCOUNT

END

This should do the changes in batch sizes of 1000...

Read MSDE 2000 product overview here. It was 5 with MSDE 1 (7.0 engine) which I was unaware recently they had changed to 25 in MSDE 2000.

http://www.microsoft.com/sql/evaluation/overview/default.asp

Now I am curious on how Oralce does it. Anyone got an up and running copy of Oralce for Windows they can test with. If not may have to install...

I enjoy the low level questions like this that don't have a easily identifiable white paper on them. Makes for fun to see how much I and how many ways...

Ok I see what stewart is saying and can verify that is right.

If the data is overwritten by all 0s for instance first that will change but this is only...

You are just needing to copy the data from Progress Database to your SQL Server? If so then as long as you have the client installed on the SQL server...

Sounds to me like MSDE may suite you just fine and work on the desktop you mentioned. Some may say more is better but if you want to impress do...

Just tried. Made no difference.

Made no difference. I replace 1 chracter per 1 chracter and was still intact just not visible directly.

I have the test files I just worked with if anyone wants to...

Note in the test it was all data. I was complete taken off guard by test results. Doesn't mean it won't eventually go away but testing shows it remains for...

Seems to be the case it is moved to another page (the entire page) from what I can tell even thou I don't see a page number change. Even tried...

Sorry, went and test myself. The data is still there even after a delete. The pointer on the page to the record is invalidated is all. But even more interesting...

Most likely a permissions issue. Right click the job and view hsitory then step details to see what it says is the error if available. This si the first thing...

If you are using SQL 7 you cannot do (at least I believe that is right sorry, only a 2000 instance handy). If 2000 then when you create the "Execute...