Adding extended stored procedures
Extended stored procedures are procedures that can be called by the Provider using an SQL command. Stored procedure syntax is not supported in the Provider's SQL grammar. However, you can install and register new functionality using extended stored procedures. UNICOM Intelligence Data Model provides the following stored procedures:
Stored procedures
xp_syncdb
Synchronizes the variables in the connected data store with the MDM document set in the MDM object property. The VDATA or HDATA table will be synchronized based on the SyncType parameter. This stored procedure fails if a metadata source is not supplied.
VDATA is default value when the SyncType parameter is not specified.
Parameters:
SyncType=[‘VDATA’| ’HDATA’]
xp_syncmd
Synchronizes the MDM document set in the MDM object property with the variables in the connected data store. Only simple variable types in the VDATA table can be synchronized. This stored procedure fails if a metadata source is not supplied.
Parameters:
None
xp_changeschema
Upgrades a relational MR database from an earlier to a later version of the schema. For more information, see
Upgrading older databases to the RDB DSC 2 schema.
Parameters:
DeleteOldData = [True | False], SchemaVersion = <version>
Extended stored procedures are implemented as extended stored procedure components. These components should register as mrOleDB mrXStoredProc components and must expose the interface detailed in the Reference section.
Registration of mrXStoredProc components
The mrXStoredProc component should be a self-registering coclass. Additional to COM registration, the component should create a new key under:
HKEY_LOCAL_MACHINE\Software\SPSS\MR XStoredProc
Add the new key value as:
Key name
The name of the extended stored procedure component: for example, mrXProc.
Default value
The description of the component.
A single value should be added under the key:
Value name
ProcClass
Value
The version independent ProgID of the component.
See also