RE: Database Lookup Functoid Connection String



Hi,

A OLE DB provider is a COM component which implement a number of COM
interfaces for OLE DB aware applications.

The XXXX part of "Provider=XXXX " is a COM ProgID which is available in the
registry HKEY_CLASSES_ROOT\XXXX. This is sort of friendly name of a GUID
called CLSID which serves a way to identify unique COM component.

In this case, SQLOLEDB and SQLOLEDB.1 are both assigned to the same CLSID.
So you can use either one. The difference here is that the first one may
map to new version when new version is available and the second one is
version specific, which means it will give you ability to run side-by-side
when next version is available. I actually suggest you use the second one
to provide maximum compatibility in future.

And connection string is a way to initialize a OLE DB provider. Different
OLE DB provider may use different connection string. In this case, you're
using Microsoft OLE DB Provider for SQL Server. And to me, it looks like
your connection string is fine, but you should be aware that the DB will be
accessed by the BizTalk server account, so the BizTalk server account
should have permission to the specified DB.

Here is a tip that may help you to build the connection string for any OLE
DB provider.

1. Create an empty text file that has an extension ".udl". Say test.udl.
2. Double-click the test.udl.
3. You will see Data Link Properties dialog. You can select a provider and
set connection parameters using nice UI rather than the encryptic
connection string directly.
4. Now when you're done, click OK to close the dialog.
5. Take a look at the test.udl file using regular text editor such as
Notepad. You will see connection string there. You can copy it.

I hope this help you.

Thanks,
Sunghwa

--------------------
| Thread-Topic: Database Lookup Functoid Connection String
| thread-index: AcV48HXZXoSZ91AnSvKQzS9U+Jt0MQ==
| X-WBNR-Posting-Host: 207.47.113.30
| From: =?Utf-8?B?UkFC?= <RAB@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Database Lookup Functoid Connection String
| Date: Fri, 24 Jun 2005 12:11:01 -0700
| Lines: 11
| Message-ID: <FA6894DE-5515-41A9-9433-00776328480F@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:14997
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| What is SQLOLEDB.1
|
| What is the ".1" at the end for?
|
| My connection string is as follows:
| Provider=SQLOLEDB;Integrated Security=SSPI;Persist Security
| Info=False;Initial Catalog=Natren_Inc_MSCRM;Data Source=SRV-DEV-CRM
|
| Is this correct, or do I need that .1 at the end.
|
| -Thanks.
|

.



Relevant Pages

  • Re: ODBC Drivers error 80040e31
    ... I've changed the connection string and am connecting with OLE DB provider now...we'll see if it makes any difference... ... Aaron Bertrand ...
    (microsoft.public.sqlserver.server)
  • Re: Delphi 7, MySQL and ADO
    ... The problem lies in the fact that the OLE DB ... provider from www.MySQL.com is from year 2001 and does not work correctly. ... want to use MySQL with ADO you'll have to do it through the ODBC, ... To be more concrete, when you create your connection string, you should ...
    (borland.public.delphi.database.ado)
  • DBPROP_INIT_PROMPT implementation
    ... goto EXIT; ... "Format of the initialization string does not conform to the OLE DB ... It works fine if I pass connection string removing last property, ... OUR provider returns DBPROMPT_NOPROMPT ...
    (microsoft.public.data.oledb)
  • Extended Properties of Microsoft.Jet.4.0 Provider
    ... Where can I get a detailed reference pertaining to the Extended Properties in ... the Connection String regarding the Microsoft.Jet.4.0 OLE DB ... Provider i.e. what the available parameters are for dealing with ...
    (microsoft.public.data.oledb)
  • Linked server to as400 - for the love of god please help.
    ... i'm trying to setup a linked server between SQL Server and an AS400/DB2/IBM ... OLE DB provider 'MSDASQL' reported an error. ... OLE DB error trace [OLE/DB Provider 'IBMDA400' IColumnsInfo::MapColumnIDs ...
    (microsoft.public.sqlserver.server)