Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is the difference between a super user (stored in cred.dat) and the indexing user, who is probably also a super user (but is stored in the vgwodbc.auth file)?

0
10 Posted

What is the difference between a super user (stored in cred.dat) and the indexing user, who is probably also a super user (but is stored in the vgwodbc.auth file)?

0
10

The Super user is intended to be the user who has READ/SELECT access to all data being indexed. This user is used to get table/view information and ultimately is the user who pulls the data from the database for indexing. Also, the super user needs to have SELECT, DELETE, and UPDATE access to event tables. Super user is typically someone with dbo (database owner) type privileges on a database schema and tables. The credentials for the super user are stored in cred.dat and are used exclusively by the ODBC gateway. An indexing user is the user whose access rights will filter the data which will be indexed. This provides table level filtering of data when it comes to indexing. In the case of databases which support column level security, a less privileged indexing user will result in field filtering when indexing. The credentials for the indexing user are stored in vgwodbc.auth and is used exclusively by the Verity Spider or K2 Spider. StyleSet Editor, by default, uses the same set of cre

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123