Sql Server syntax for updating using a case statement:

update table_1

set Datum2=(case when datum1='1' then 'One'

when datum1='2' then 'two'

when datum1='3' then 'three'

else 'four' end)

In case you're not sure of how to unit test it without running the full application use the Query Analyzer, or in the case of 2005 click the 'New Query'...

I notice  that the 'Date' is a common field in the Header line and that there is a common seperator, the pipe.

Here is a very general example of an attack...

I know this is going to cause 'Howls' of disbelief but if you are NOT using the transaction logs at this point to rollback transactions by the hour or whatever...

I agree with 'Sql Oracle' on this one except for one thing. You would probably want to maintain your unique ID field. It's a good idea and can come in...

I've seen the Sql Native Client referred to when using the Business Intelligence Developement Studio's Import SSIS Import/Export Wizard. Here what the help file says:

SQL Native Client is a data...

It's strange that the table would list the number of records bound by the size of a small int. Is it possible that your unique ID field, (assuming you're using...

I guess I'm confused by the terms 'Total Record Count'OR CalcAction='Record Count of Unique Claims ', I'll assume that these are counts of actual record conditions. Also the order by...

I'm not sure why you don't create an identity column, (type Int or BigInt), in the table that you're storing the records to. That way you don't need any code, Sql...

I agree that the table isn't in good shape, but in the real world 'Stuff happens'. Assuming that there is a correct common key that you can link the partial...

Right, For this reason the scheduled process would have to be aware of the name change. They'd have to be written so that they ran against, JFK instead of FDR.

Assuming that you really want to make this table unavailable to the users/system during this process you can simply rename the table and rename it back when done, i.e.: