As Scott said, a cursor is just that, too.

You'd load them back into sqlserver....

Seriously why do you want to take those records out of the database?

How many records r u talking about?

Select *

FROM tablename

WHERE datefield > '1/1/2005'

This is assuming you're having a syntaxe error..

What results did you get... what did you want to have?

Can you do something like this?

Alter DB

begin tran

exec 1

if @@error 0

quitwithRollback

exec 2

if @@error 0

quitwithRollback

...

exec 4

...

no error :

commit tran

return 0

quitwithrollback

rollback tran

return 1

if the return code is 1 then...

Exactly.

Most likely explanation...

I swear I'm gonna kill the next guy who proposes a dynimaic sql solution for this problem. Guys learn how to code pls b4 answering questions.

Well one thing you could do assuming I know what you want to do next is just update the field to upper case :

Update dbo.YourTable set YourField = UPPER(YourField)

Or...

Same thing except that insert into is the ainsi standard that you should use.

That's nice but that will ALWAYS result in a scan of the table or index. You'll never get any real performance on larger tables... and it's gonna be a...

A command console and a console command doesn't ring the same to my hear.. or does it?

Select * from master.dbo.syscursorcolumns

@@FETCH_STATUS is a global variable telling you if the fetch was successfull.

This is an exemple of a cursor (that would have absolutely no use...)

DECLARE Employee_Cursor CURSOR FOR

SELECT LastName, FirstName FROM...

Sorry about the reversed Cs but I translated from french and looks like I was wrong.

Numeric(6,4) = 6 numbers, 4 decimals (00.0000)

(10,4) = 10 numbers, 4 decimals (000000.0000)