as for the original topic of this forum. I've just wasted 30 minutes of oxygen to have to explain (after no details added) that emptystring is not the same as...

blank is not NULL,it is emptystring - you need to use DBNULL

if you are passing empty strings in then how does sql know if you want to set the value...

ok - here is an example that does not null out your columns

CREATE TABLE x (id int, firstname VARCHAR(50),lastname VARCHAR(50))
GO
INSERT INTO x SELECT 1,'mike','jones'
go

CREATE PROC upd @id...

give me 2 minutes and i'll get you a working example

Well this is what I have below, and if the parameter is NULL it is wiping it out.

Am I doing it wrong somehow?

UPDATE [dbo].[DebtorACH]
SET first_name =...

nope - both phil and my solution set the value to itself if the parameter...

that wont fix the OP's issue - all that will...

I know this might sound stupid, but check to see if all of your parameters are NULL - then don't update a row that is setting itself to itself.

phil's idea is better than mine

or even better, rather than building up the table variable inside the proc , could you pass a TVP through?

just a thought (might be a bad one)

build a table variable or temp table and put the values in there in a format that mimics the target table (as a...

It gets weirder and weirder. The row with PK value "0000001" did have 2 another fields which were empty. This did make this row faulty in real-life (but from...

most likely nothing has happened to the installation of your database server.

More than likely it is the input file or the input process

how about using an "if not exists then...

ok

we probably need to see the SQL that is being executed, but 15k records is very small for SQL. are you trying to put them all on screen in a...

is your reason for switching to read only mode just to preserve the original database?

at that point the AG becomes useless anyway - so break the AG.. if you can...