SharePoint Connection

SQL Server 2005, 2008, 2008R2, 2012, 2014

SQL Server 2005, 2008, 2008R2, 2012, 2014

All Downloads ----- Join VIP ----- Questions?

Overview

SharePoint Connection Manager is SSIS Connection Manager for establishing SharePoint connections. Use the API to build components based on SharePoint Connection Manager.


Setup

Use the SharePoint Connection Manager dialog to specify parameters for connecting to SharePoint service.

Server Options

Deployment

Specify deployment type. This parameter has the options listed in the following table.

Value Description
Premise Connect to on-premise SharePoint server.
Online Connect to SharePoint Online (Office 365) service.
Server

Specify the name or IP address of the SharePoint server.

User name

Specify user name to access SharePoint. If not specified, the connection will be established using Windows authentication.

Password

Specify password to access SharePoint.

Time-out (secs)

Specify the number of seconds before timing out session connect. The default value of this parameter is 100 seconds.

RetainSameConnection

Specify if all clients should use the same connection. This parameter has the options listed in the following table.

Value Description
True All clients use same connection (default).
False Every client use different connection.
Test Connection

Confirm connection manager configuration by clicking Test Connection.

Proxy Options

Host

Specify the name or IP address of the proxy server. If not specified, proxy server is not used.

Port

Specify the port number on the proxy server to use for the connection.

User name

Specify user name to access the proxy server.

Password

Specify password to access the proxy server.

How to trace the web services calls in use?

You can use the regular .NET network tracing facilities to trace the web services calls. Follow these steps to enable tracing:

  1. Go to DTS\Binn folder and open DtsDebugHost.exe.config file in your favorite text editor.
  2. Include following settings inside configuration element:
        <system.diagnostics>
          <trace autoflush="true" />
          <sources>
            <source name="System.Net" maxdatasize="1024" tracemode="protocolonly">
              <listeners>
                <add name="MyTraceFile" />
              </listeners>
            </source>
          </sources>
          <sharedListeners>
            <add
              name="MyTraceFile"
              type="System.Diagnostics.TextWriterTraceListener"
              initializeData="c:\System.Net.trace.log" />
          </sharedListeners>
          <switches>
            <add name="System.Net" value="Verbose" />
          </switches>
        </system.diagnostics>
    

initializeData attribute controls where the trace log file is saved. Now when you execute a package inside Visual Studio, "c:\System.Net.trace.log" file will contain the web services tracing information. If you want to trace when you execute packages outside Visual Studio, include the settings above in DTExec.exe.config configuration file.

Make sure you comment or remove the tracing settings after you finish testing. Otherwise this may slow down your package execution speed considerably.