Purging PCI data from Old SMSMkt database

Purging PCI data from Old SMSMkt database

Periodically, Pebble beach will find some PCI data in their Marketing Module.  This is the old Marketing Module, so it isn't checking for CC# in all the fields like comment or phone #, etc.

 

So Alan Fujii will send a list of tables with bad values they contain.  For any table that begins with a Z, instead of fixing the issue in the Z table itself, use the name of the Z table to find the root location of the bad data.  For example, zGuestInfo_Phone1, instead of cleansing that table, do the following:

 

  1. In SQL Management Studio, navigate to the database, and then tables, and right click on the GuestInfo table

 

  1. On the menu select Edit Top 200 records
  2. Once the grid is open, press Ctrl+3 or select on the menu, Query Designer -> Pane -> SQL
  3. With the SQL query now available, add an appropriate WHERE clause, using the LIKE operator and wildcard characters around the example segment you've been given.  In the above example WHERE phone1 LIKE '%488860%'
  4. Find the record and check the GuestinfoBatchTimeStamp or ResinfoBatchTimeStamp, if from the current day, this information is going to repopulate at the next run, and PB needs to correct in the SMS system.  Such corrections will automatically feed into the table at the next run, requiring no further editing.
  5. replace the credit card information with the words PCI REDACTED
  6. After completing the edit, click the mouse in another field.
  7. Change the Where clause to the next number to be redacted and contiue.
  8. Z tables will be updated with the Redaction notices after the next schedule run of the SMSMkt interface.

    • Related Articles

    • Interface Delphi2008 - How to stop data from being extracted for a property in a multi-properties scenario

      Following are the instructions on how to de-activate data extraction for a property.   Make a backup of the Access database CountryStateCodeLookUps.mdb and put it into the _Archive folder. Preferred naming convention of backup is ...
    • Clearing 'stuck' data writes in DVUpload Status

      Get a list of what is currently outstanding:   select * from DVENTERPRISE.dbo.StagingRequests where StatusId < 4   Fail those currently outstanding records   Update DVENTERPRISE.dbo.StagingRequests Set StatusId = 5 where StatusId < 4
    • DVAlert Error - Number of records don't match between tmp and inc...

      So, DVAlert is failing, the message is something like this: "IdBatch: 658 The numbers of records between tmpfactPMSBOB and incfactPMSBOB not match for cube PMS BOB" The problem is most likely that one of more of the dimensions has duplicate All ...
    • Steps to Fix Rigid Relationships Error

      First search and open Visual Studio        ·         Go to “File” in the top left corner, then go to “Open”, and click on “Analysis Service Database” ·         Select the Datavision Database and click “OK” ·         It will take a couple of minutes ...
    • How to load missing dates for Givex

      Below is a brief description of what needs to happen when the Givex file is late or is not received by Givex.  I am typing this up for all in the office so they are aware of the steps.   Whenever we receive these types of messages, we need to deal ...