Creating an EDM indexed profile from a MSSQL server. Note: The Administrator guide states that The SQL Preindexer only supports Oracle databases.
If you are using the SQL Preindexer with MSSQL databases, the support is "best effort" support, this is not a certified solution.
You would like to create an EDM for the Enforce DLP system to use, however the SQLPreindexer is only certified and supported on the oracle database systems.
Creating an EDM for MSSQL Databases without using the SQLPreindexer DLP solution:
Creating and EDM from a datasource involves getting the datasource in the correct format on the Enforce server, and then configuring a EDM data profile to use the data source file and create the EDM.
On the MSSQL server, you can will need to create a query to pull the wanted data from your database. After the query is pulling the correct data and fields you want to use for your EDM, you can then export the query results as a CSV file, comma, pipe, or tab delimited. Copy the exported CSV file to the "datafiles" folder on the enforce system, and then you can create your EDM using the copied CSV file as your data source.
Note: When creating a csv file from the MSSQL server, it will not be encrypted, therefore it is like copying a csv file to enforce server to use to create the EDM profile.
a) on MSSQL create a query to pull the data you would like to use for the EDM profile. Note: an EDM profile is best to have at least 2 to 3 fields for better indexing.
b) run the query and make sure the results or data is what you would like to use. i.e "Select FirstName, LastName, EmailAddress from Person.Contact" using AdventureWorks test database.
c) Once query is correct, you can either export the results to a CSV file, or create a SSIS package with integration services to automate the process. Basically you are just creating a CSV file that the enforce server can use to create the EDM profile. You will want to get the exported CSV file to enforce sever under drive:\SymantecDLP\protect\datafiles\edm_mssql_output_csv Note: you can name the file whatever you want, just make sure the file is on proper place on enforce server and matches the csv outputted filename from mssql server.
d) On Enforce server go to Manage --> then Data Profiles ---> Exact Data click on add Exact Data Profile. Give data profile a name.
e) Click on "Use This File Name" and give a name as edm_mssql_output_csv to match the exported CSV file from the MSSQL database. Number of columns 3 in our example, choose the comma delimited option and leave the 5% error threshold, then click next Note: The filename must match exactly the file exported from the mssql server.
f) Col 1 = firstname Col 2 = LastName Col 3 = email in our example. Also, you may check the box Submit Indexing Job on Schedule and choose daily or weekly etc.. on how often the EDM profile is indexed.
Note: Once Enforce server indexes the file, in our case the drive:\SymantecDLP\protect\datafiles\edm_mssql_output_csv file according to schedule it will delete the source file so it will no longer be in the Vontu\Protect \datafiles directory. You can schedule your SSIS package to export the file daily @ 6:00 pm, and Schedule the Index Job to run @ 7:00 pm. This way you get up to date data for your EDM profile.
Microsoft MSSQL databases 2005, 2008, and 2012 versions.
Imported Document ID: TECH219445
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe