Profiling System: OLEDB Data Source Dialog Box

Article
11/12/2009

This is the second of two Profiling System dialog boxes that is displayed when you unpack a site using Commerce Server Site Packager. This dialog box is not displayed when you unpack the SupplierActiveDirectory Solution Site.

The following table shows the options and functions available in the Profiling System: OLEDB Data Source dialog box. If you are unpacking a Solution Site, click Next to accept the default entries.

Use this	To do this
Modify	Accept the default connection string to the Profiles database, or click Modify to configure a new connection string.
Schema definition scripts	To pack the profile definitions, use SQL Server Enterprise Manager to export the definitions (schema) from the SQL database to a .sql file, and then specify the name of that file here. When you unpack your site, you will specify this file so the definitions will be unpacked into the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.). For more information, see Packaging Extended Profile Schema.
Data population scripts	If you have extracted the profile data from a Profiles database, you can specify data population scripts so when you unpack, the profile data is imported into the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.). For a sample script that contains data for two users, see PopulateProfileSql.sql, which is located in \Program Files\Microsoft Commerce Server 2002. For information about using scripts with site packager, see Using Scripts with Site Packager.

Modify

Accept the default connection string to the Profiles database, or click Modify to configure a new connection string.

Schema definition scripts

To pack the profile definitions, use SQL Server Enterprise Manager to export the definitions (schema) from the SQL database to a .sql file, and then specify the name of that file here.

When you unpack your site, you will specify this file so the definitions will be unpacked into the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.).

For more information, see Packaging Extended Profile Schema.

Data population scripts

If you have extracted the profile data from a Profiles database, you can specify data population scripts so when you unpack, the profile data is imported into the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.).

For a sample script that contains data for two users, see PopulateProfileSql.sql, which is located in \Program Files\Microsoft Commerce Server 2002.

For information about using scripts with site packager, see Using Scripts with Site Packager.

Share via

Profiling System: OLEDB Data Source Dialog Box

See Also

Additional resources