I think that even you are capable of doing a "update t set firstname = 'xxxx' from mytbl" without the need to give you examples from the net.

if the application is going to remain active (or while it remains active until its usage/data is migrated to another application) I would leave it on its own database -...

you changed something on your script as the output you had given before meant the script supplied by Scott worked.

you may have dropped 1 column from the table definition (or...

stored procs is the easiest and fastest to implement for a small scale like that.

restore prod db to another instance (protected), run data desensitization process, backup and make backup available...

WHAT!!!!!!

Non Prod SHOULD NOT have PII information.

Get your processes changed so dev gets a version of the prod database that has gone through a process of removing PII information from...

changing part of Scott's code should work.

SELECT @sql = STUFF((
    SELECT ', ' + 'MOVE ''' + LogicalName + ''' TO ''' 
 ...

• This reply was modified 4 years, 9 months ago by frederico_fonseca.

DDM is NOT a good choice for anything - for ad-hoc users its not like they can unmask it but they can infer the data and after multiple attempts they...

as a important note get ride of those with(nolock). if your business is ok with possibility of having bad data supplied to them you can add a single statement at...

Social Security numbers are considered PII and are a attribute of an individual/company and should be stored securely and are for this reason a bad choice for PK - other...

the following code will work - .mdf file CAN NOT be opened by SQL Server when it is done as SQL will exclusively lock the file.

as everyone said this is...

• This reply was modified 4 years, 9 months ago by frederico_fonseca.

yes - but by giving them those pages on a file...

you can - but it would be completely useless for any intents and purposes. small c# program open file binary, read first 25 pages (25*8k bytes) and do same for...

not wishing to minimize the article itself which I consider well written I wonder why would posting this on a SQL Server forum be a good idea.

No issues from a compatibility point of view for having both running on same box - obviously resource sharing is where one may impact the other but if both are...

not sure if it was just a typo but the example supplied is only adding a single quote to the item on the middle - so clarification on the requirements...