Microsoft awards DataSplice Gold Certified Partner Status
ADO.NET Data Source Configuration
Select the ADO.NET Data Source from the list of available Server Plug-ins to display its options:
Basic Settings
The following settings control various aspects of how the ADO.NET plug-in operates. The default options are fairly reasonable and rarely need to be changed:
| Query Cache Timeout | Specifies the time, in seconds, that schema information for a query is cached. |
|---|---|
| Stored Procedure Cache Timeout | Specifies the time, in seconds, that information regarding stored procedures is cached. |
| Maximum Records Fetched | Controls the maximum number of records that can be returned by any single query. This is used primarily to prevent runaway offline that transfer unreasonably large amounts of data to a handheld. Increase this value to the maximum number of records that are needed offline for any particular view. |
Connection Profiles
The DataSplice Server uses connection profiles to define the settings used to connect to external data sources. Each view specifies a particular connection profile to use.
Connection profiles allow settings for multiple views to be quickly changed, since the details only need to be modified for the connection profile once. Note that it is strongly recommended that connection profile names refer to the generic application being accessed (maximo, tools, etc.) and not include any stage information (maxdev). Each view will reference the connection profile by name, and this allows the settings to be clear when copying views to the various stage instances.
To create a new connection profile, click the Add New Section button to create a new entry. This has the following options:
| Name | This is the unique name used by DataSplice to identify this
connection profile. This name is referenced by all DataSplice views to
specify the data source to gather data from. The name is case-sensitive. |
|---|---|
| Driver | This drop-down menu contains the available native database drivers. Select the corresponding driver describing the specific platform in use. |
| Database Server | This is the server entry in a valid ADO.NET connection string. For Oracle, the server entry usually corresponds to a tns entry. In SQL Server, the server entry is usually the name of the machine where the database resides. |
| User Name |
This is the user name that the DataSplice Server will use to connect to the data source. This user should have sufficient permissions to access the target data. |
| Password | The password associated with the specified User Name. |
| Initial Catalog |
When applicable, this is the database instance to use when multiple
databases are present. For SQL Server this specifies the name of the
database to use. For Oracle connections this specifies the default
connection schema. |
| Trusted Connection |
When this check box is enabled, the same credentials used to launch
the DataSplice Server application will be used to authenticate against
the database. The User Name and Password fields are ignored in this case. |
| Extra Options |
This allows additional connection settings to be passed to the database in the connect statement by appending this value to the basic connect statement generated by DataSplice. Consult the documentation for the database provider for a list of valid parameters. |
| Pass-Through Authentication |
When this check box is enabled, the plug-in will pass-through to
the database the user name and password supplied by the user in the
Remote Client. This requires the accounts used by DataSplice to have
valid corresponding accounts in the database. This will usually cause
the server to keep more connections to the database open, so it should
only be used if a single connection account will not work for some
reason. |
| Verify Connection |
When this check box is enabled, upon saving the connection profile
settings, DataSplice attempts to connect to the data source to ensure
that the settings are correct. This is useful for saving profile
settings when the database server is currently unavailable. |
ADO.NET Drivers
Several different drivers are available to allow DataSplice to connect to various back-end databases. In practice the most important are
- Microsoft SQL Server
- This provider is installed with the .NET framework and uses native connections to ensure the highest performance and functionality available. If supports both SQL Server 2000 and SQL Server 2005.
- Oracle ODP.NET 10/11
- There are several options for connecting to Oracle, but the best choice is to use the latest version of ODP.NET. This driver supports database versions 8.1.7 through 11g and is available for download from Oracle's website.
Other drivers are available (MySql, DB2, etc) but are not enabled by default and cannot be guaranteed to support the range of functionality supported with SQL Server and Oracle.
