OLEDB can be used with VBScript jobs in 24x7. You will not be able to use profiles
but you can still hard code connection parameters just as you do it in Visual Basic programs.
If you wish you can store connection parameters in INI or TEXT files and read them dynamically in
script jobs. On the other hand why don't you use the native database connection
instead of an ODBC? Just create a profile under Microsoft SQL Server branch. : Under Database Profiles I see that you can configure
: a connection to a SQL Server 7.0 database via ODBC.
: I don't see a way to configure SQLOLEDB as a
: Provider. Is there a way? if so, how do you configure it. : This change was prompted by the fact that via ODBC, fatal
: SQL errors are not passed back to the client (24x7), but
: via OLEDB they are. We have tested this using Visual
: Basic 6.0. The following SQL command returned an error
: using OLEDB, but nothing using ODBC. : Select Convert(int, 999999999999999) : The error return using OLEDB is as follows. : Server: Msg 8115, Level 16, State 3, Line 1
: Arithmetic overflow error converting numeric to data type int. : Nothing from ODBC. : Can you help me with this problem?
: thanks,
: Sam Mills
|
