When installing Precise for SQL Server, in a Precise version prior to version 8.0, you are asked to use a login account that has System Administrator privileges. Although it is strongly recommended to run Precise for SQL Server with a System Administrator user, in Precise version 8.0 and higher, it is also possible to use a less powerful login account.

In any case there are a few privileges that you need to grant to that login account:

• The privilege to alter a trace.
• The privilege to view any definition.
• The privilege to control the server.

Take into consideration, that when you run Precise for SQL Server with a login account that is not System Administrator, you will miss the following functionality:

• DBCC TRACEON. This may increase the number of sessions that have a NULL batch handle and therefore increase the amount of Text N/A batches.
  Workaround: You can add DBCC TRACEON 2861 in the starting parameter of the SQL Server instance (-T 2861).
• DBCC INPUTBUFFER (if needed by the internal collector logic). This may limit the ability the retrieve the statement/batch text when the system encounters some known bugs in SQL Server.
• Metrics for not responding transactions. You will get an error in Alerts.
• Show statistics and Show config views enabled in index/table entities in the Objects tab. They will stop working.
• Recommendations. This may limit to get recommendation for objects and statements.

For more information, see Start and Use the Database Engine Tuning Advisor on the MSDN website.