Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
francislodwick
Starting Member
1 Post |
 Posted - 2012-10-17 : 09:18:07
|
| I've been working on a new database in SQL Server 2008 which is used by call-centre agents to make sales on various products. During the day, these agents will accept credit card details and store them temporarily before processing. At night, the database is backed up, but we can't backup the credit card details for obvious security reasons. At first I thought just to UPDATE the credit card fields to NULL before backing up using the standard BACKUP procedure, but it turns out that the details need to be kept in the original database, in case they haven't been processed that day. All the sensitive credit card details are contained in one column of one table.Just to be clear, putting the sensitive tables in their own filegroup and then backing up filegroups selectively wouldn't work, because we want the data contained in the tables -- customer name, telephone etc. -- everything, that is, except the values of the credit card fields.Currently the only idea I have is making a temporary copy of the whole database, updating the credit card fields to null in that, and then backing that copy up; but this is obviously not an ideal solution.I have a feeling this should be straightforward, but I'm a newcomer (this week) to both databases and T-SQL, so any hints or directions would be much appreciated. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2012-10-17 : 09:43:18
|
So you say it is ok to store that informationen in a table/column but then to take the backup isn't ok?Ok, you've called it "store them temporarily", but does the time really matter?Take a payment service provider and all the problems are gone...
Too old to Rock'n'Roll too young to die. |
 |
|
|
|
|
|
|
|
Auto deleting credit card details in db backup