GetAuditDataByLocation 2008/06

The GetAuditDataByLocation stored procedure retrieves audit data from AVEVA™ Production Management and delivers it to an external SQL database.

Note: Windows authentication is not supported for CLR Stored Procedure.

Returned data

The GetAuditDataByLocation stored procedure returns data in a database table with these columns.

Parameters

The GetAuditDataByLocationV200806 stored procedure contains the following parameters:

• module

  Module is a mandatory parameter used to specify the module used in the query.

  For example: Maintenance

• location

  Location is a mandatory parameter used to specify the reporting point for the query.

  For example: Plant.Area 1.Downtime 1

• setId

  The ID of the record to get audit data.

• editedBy

  Filters by who edited the record.

• samplePeriod

  Sample period is the period of time to use in the query. This can be any filterable period definition or date time.

  • SamplePeriod uses UTC time

  If you specify both start and end date times as well as a sample period, the sample period takes priority and the start/end date times are not used.

• startDateLocalTime

  Specifies the start date and time for a query, where the time is specified in local time.

  For example: 01 May, 2008 11:00:00 AM

• endDateLocalTime

  Specifies an end query date that uses a date time format that is specified in local time.

  For example: 01 May, 2008 10:00:00 AM

• username

  Specifies an AVEVA™ Production Management user name to use as Basic security.

• password

  Specifies a password for the username.

• serverName

  Specifies the default base URL to use for the Web services.

  Example:

  http://localhost:8889/test

  It is important that the base URL ends in a forward slash (/).

  The default endpoint is added to the default base to make a complete URL.

  Example:

  http://localhost:8889/Ampla/WebService/Data/2008/06

• session

  The session parameter enables passing the same security credentials as the user in AVEVA™ Production Management. Previously, the CLR stored procedure permitted only passing Username and Password as security parameters.

  Enter the unique identifier for the session to access credentials for that session.

  For example: 8e65edfb-e81e-4891-aefa-f61ac18ba79b

Related topics

• GetDataByLocation 2008/06

• CLR Stored Procedure