Following are the steps I used to get parameters mapped to my SQL query using DataReader Source  and ADO.Net connection manager.

1. Create Ado.Net Connection manager using .Net Providers.

2. Add DataReader source and map it to ADO.Net connection manager by right Click -> Edit.

3. Under component properties, Write SQL Command without where clause.

4. Verify Column mapping and click ok to close the DataReader source editor.

5. Go to Control Flow and go to properties of Data Flow Task. Notice a property called Expression and an a small button next to it. Click on this button to open expression editor.

6. In Expression editor select[ DataReader Source].[SQLComamnd] under property column and hit small button under expression column, This would open another editor.

7. Write in your SQL query appended with variable names and hit Evaluate expression button

Note: On hitting Evaluate expression, You could see evaluated value box populated with variable value(in my case its date 12-07-2005 04:01:00.

8. Rest of the stuff is same, You could go to data flow tab and map the output of your DataReader task to valid output task.

Note : Execution succeeded but there is still a red cross which I guess is there because of same runtime evaluation of expression V/S design time value. I am not sure if there is something that could be done about it but I guess for now if it works, You could safely ignore it.

Doing similar operation with OLEDB Source

Create a data flow task and place an OLEDB source and Flat text Destination.

In OLEDB Source’s SQL command, I used  select * from sys.sysprocesses where last_batch >= ?

And mapped query parameter with MyDateType by clicking Parameters button.

Although preview won’t work at this point but if I would execute the package, I see query with DataType parameter fetching relevant data without any exception and dumping it in text file for validation.

These are typical symptoms.

1. You have your SSIS package using Oracle OLEDB provider for one or more connection managers.

2. You have recently installed oracle client.

3. Your server hosting SQL Agent and Oracle client was not re-started after installation of oracle client.

4. SSIS package runs fine from BIDS as well as command prompt using DTExec utility.

5. SQL Agent job running the same SSIS package goes into perpetual execution, it neither finishes nor error out giving illusion of hang situation.

Cause

After your install oracle client, the information about oracle client installation directory and bin folder is stored in environment variables. Any application using oracle client would read the environment variables at its startup and would load needed dll from Oracle home directory. Services like SQL Agent which are running before the installation of Oracle Client will have old environment variable values as a result any thread spawned by SQL Agent will not be aware of the location of oracle client DLLs.

Ideally, any process not being able to load required DLLs would throw an error message in form of windows message box but since SQL agent is a service and not a console application it is not able to create a handle for this message box window. Result is, the error message box never shows up to the end users. This creates a deadlock: Job execution has thrown error message box which SQL agent cannot draw, and until this message box is drawn and the user clicks OK or Cancel button, The job execution won’t finish/terminate.

What to do ?

After installing Oracle client, Re-start your computer. If re-starting computer is not possible, Re-starting SQL agent should resolve the problem as process re-start would re-load new environment variable values with correct oracle installation path values.

I created a simple SSIS package using a connection manager going to SQL Server using SQL authentication, I have my ProtectionLevel as EncryptSensitiveWithUserKey

My package has an OLEDB Source (using connection manager above) which queries a table in database and dumps few rows in flat file.

With above settings ,when I execute my package, Its works like a charm.

Now, I changed the ProtectionLevel  to DontSaveSensitive

And package failed

With following error

SSIS package "Package.dtsx" starting.

Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.

Error: 0xC0202009 at Package, Connection manager "runeet2k8.sa": An OLE DB error has occurred. Error code: 0x80040E4D.

An OLE DB record is available.  Source: "Microsoft SQL Native Client"  Hresult: 0x80040E4D  Description: "Login failed for user 'sa'.".

Error: 0xC020801C at Data Flow Task, OLE DB Source [1]: The AcquireConnection method call to the connection manager "runeet2k8.sa" failed with error code 0xC0202009.

Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.

Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation.

Error: 0xC0024107 at Data Flow Task: There were errors during task validation.

SSIS package "Package.dtsx" finished: Failure.

What we see above is expected as we have sensitive information in our package (password for SQL account) and have chosen DontSaveSensitive as protection level. The affect is Password being cleared from our connection manager hence login failure.

For this situation, We would have to save this password somewhere outside the package. I chose to save it in configuration file as shown below. I used XML Configuration file

I had to chose correct connection manager, Its called runeet2k8.sa in my case

This is the XML configuration file that BIDS wrote for me

<?xml version="1.0"?>

<DTSConfiguration>

      <DTSConfigurationHeading>

            <DTSConfigurationFileInfo GeneratedBy="Domain\UserName" GeneratedFromPackageName="Package" GeneratedFromPackageID="{77FB98FB-E1AF-48D9-8A43-9FD6B1790837}" GeneratedDate="22-12-2009 16:12:59"/>

      </DTSConfigurationHeading>

      <Configuration ConfiguredType="Property" Path="\Package.Connections[runeet2k8.sa].Properties[Password]" ValueType="String">

                  <ConfiguredValue></ConfiguredValue>

      </Configuration>

</DTSConfiguration>

I have to go in and type password value.

<?xml version="1.0"?>

<DTSConfiguration>

      <DTSConfigurationHeading>

            <DTSConfigurationFileInfo GeneratedBy="FAREAST\runeetv" GeneratedFromPackageName="Package" GeneratedFromPackageID="{77FB98FB-E1AF-48D9-8A43-9FD6B1790837}" GeneratedDate="22-12-2009 16:12:59"/>

      </DTSConfigurationHeading>

      <Configuration ConfiguredType="Property" Path="\Package.Connections[runeet2k8.sa].Properties[Password]" ValueType="String">

                 <ConfiguredValue>Password</ConfiguredValue>

      </Configuration>

</DTSConfiguration>

Now i have a package with ProtectionLevel as DontSaveSensitive and password value for connection manager saved in a configuration file outside the package. Package executed absolutely fine after this.

I went ahead and set this package as Integration Services Job under SQL Agent.

Executed the job and it ran successfully.

One important thing to note is that if you are moving your package from your development machine to say test server for execution. You would have to move your configuration file as well and put it at same path on target machine where its placed on your development box.

For example, on my box, the config file PackageConfig.dtsconfig  is placed at D:\Cases\Integration Services Project1\PackageConfig.dtsconfig and if I am moving my package from my development machine to somewhere else, I would have to move my config file as well and place it at location D:\Cases\Integration Services Project1\ on that machine.

If you don’t have dtsconfig at expected location, Job would fail.

If you done want to create same complex folder path for dtsconfig on target machine as its on your dev box (eg: D:\Cases\Integration Services Project1\) You could place this dtsconfig file anywhere you want and give the pointer of this path from Configuration tab  under you SSIS job step.

select Job.name as JobName
from dbo.sysjobs Job, dbo.sysjobsteps Step
where
Job.job_id=Step.job_id
and
Step.command like '%sp_linkedservers%'

eg:

<?xml version="1.0" encoding="utf-16"?>
<root>
<Name xsi:nil="true">name1</Name>
<Name xsi:nil="true">name2</Name>
<Name xsi:nil="true">name3</Name>
</root>

Ideally this is an Invalid XML but there is a way to load it in XMLDocument using following code snippet.

            XmlDocument doc = new XmlDocument();
            
            NameTable nt = new NameTable();
            XmlNamespaceManager nsmgr = new XmlNamespaceManager(nt);
            nsmgr.AddNamespace("xsi", "http://www.w3.org/2001/XMLSchema-instance");
            XmlParserContext context = new XmlParserContext(null, nsmgr, null, XmlSpace.None);
            XmlReaderSettings xset = new XmlReaderSettings();
            xset.ConformanceLevel = ConformanceLevel.Fragment;
            XmlReader rd = XmlReader.Create(new  StringReader(XMLSource), xset, context); 
              
            doc.Load(rd);

Could not find file 'C:\Documents and Settings\d108967\Local Settings\Temp\1\tmpD7.tmp'.".

The reason for this is the way this SSIS package work. If you open this package in BIDS you would see many File System Connection managers pointing back to files in TEMP directory i.e.

AllowedToFailPrologueSql pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6AC1.tmp
InnerPackage.dtsx pointing to C:\Users\runeetv\AppData\Local\Temp\1\InnerPackage.dtsx
PostTransactionSql pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6AC2.tmp
CompensatingSql pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6AC0.tmp
EpilogueSql pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6ABE.tmp
NonTransactableSql pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6ABF.tmp
PrologueSql pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6ABD.tmp
TableSchema.XML pointing to C:\Users\runeetv\AppData\Local\Temp\1\tmp6ABC.tmp

If TEMP directory is cleared because of any reason, you would get “Can not find file” error messages.

If you create a new package with same tables selected and “Optimize for many tables” selected , new *.tmp files with different name would get created and old package would still fail.

• The option I see to get this work permanently is by copying these files to a another directory other then TEMP and open your package in BIDS (Business Intelligence development studio) to modify connection string of above file connection managers to your new directory.
• Second way is by not selecting “Optimize for many tables” . This option would only be useful if you are working with more than 100 tables.

Runeet Vashisht

•Microsoft.VisualBasic.dll

•Mscorlib.dll

•System.Data.dll

•System.dll

•System.Xml.dll

•Microsoft.VisualC.dll

•CustomMarshalers.dll

•System.Security.dll

•System.Web.Services.dll

•System.Data.SqlXml.dll

•System.Transactions.dll

•System.Data.OracleClient.dll

•System.Configuration.dll

If a user assembly references any .NET frameworks assembly that is outside of the ‘blessed’ list and you try to register the assembly with SQL Server, error 10301 will be raised.

Server: Msg 10301, Level 16, State 1, Line 1

Assembly 'AssemblyName' references assembly 'accessibility, version=2.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a.', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: 2(The system cannot find the file specified.)). Please load the referenced assembly into the current database and retry your request.

For e.g. : I added DataSet1 to my windows application which has a TableAdapter called GetProductionLocationTableAdapter. GetProductionLocationTableAdapter calls a stored procedure called GetProductionLocation. To modify the default timeout setting of this select command, I modified TableAdapter constructor in DataSet1.Designer.cs as shown below.

public GetProductionLocationTableAdapter() {
            this.ClearBeforeFill = true;
            this.CommandCollection[0].CommandTimeout = 0;
        }

If you do not want to modify default dataset code, You could extend partial TableAdapter class as follow.

public partial class GetProductionLocationTableAdapter {

    public int cmdTimeout
    {
        get
        {
            return this.CommandCollection[0].CommandTimeout;
        }

        set
        {
            this.CommandCollection[0].CommandTimeout = value;
        }
    }

You would  have to then call this property from the windows form/web form / class using this TableAdapter, For e.g. in my code I called this property in load event of the form.

private void Form1_Load(object sender, EventArgs e)
        {
            // TODO: This line of code loads data into the 'dataSet1.GetProductionLocation'    table. You can move, or remove it, as needed.
            this.getProductionLocationTableAdapter.cmdTimeout = 0; 
            this.getProductionLocationTableAdapter.Fill(this.dataSet1.GetProductionLocation);
        }

1. From your registry key HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.ini\ODBC make sure that the value for entry Trace is 1.

2. Re-Start your computer.

3. After your computer re-starts, Launch the application against which you want to collect ODBC logs and execute the activity to be logged.

4. Go to ODBC Administrator from Start ->Run -> odbcad32.

5. Go to “Tracing” tab and Click “Stop Tracing Now”

6. Go to Log file path and view the logs. You should have some information being logged now.

Note: If your operating system is 64 bit and application is 32 bit, The application would use 32-bit version of ODBC driver. You could manage 32-bit ODBC trace from c:\windows\syswow32\system32\odbcad32.exe on 64 bit Operating System.

The counters themselves will remain present in the product, however, so that code that checks for their existence doesn’t fail. For the managed SQL Client and Oracle Client, Ten new counters have been introduced .

The HardConnectsPerSecond counter was ported forward from the old ODBC performance counters. It represents the number of actual physical connections per second that are being made to a server. It ignores pooled connections, and only real database connection opens are counted.

The HardDisconnectsPerSecond was also ported from the old ODBC counters. It represents the number of actual physical disk connects per second being made to a server. It also ignores pooled connections. Only real database disconnects are counted.

The NumberOfActiveConnectionPoolGgroups is new to ADO.NET 2.0. It represents the number of unique connection strings.

The NumberOfActiveConnectionPools was ported from the CLR data counters from ADO.NET 1.0. It represents the current number of pools associated with the process or AppDomain.

The NumberOfInactiveConnectionPoolGroups is new to ADO.NET 2.0. It represents the number of unique connection strings that are waiting to be pruned by the garbage collector.

The NumberOfInactiveConnectinPools is also new in ADO.NET 2.0. It is the current number of pools associated with the process or AppDomain that are waiting to be reclaimed because they are idle. This might be a circumstance where their pool timeout, which is controlled by the connection string parameter, default = 10 minutes, has expired and they are waiting for garbage collection.

The NumberOfNonPooledConnections is also new in ADO.NET 2.0. It represents the current number of connections that are not using connection pooling.

The NumberOfPooledConnections was ported from the CLR .NET counters from 1.0. It represents the current number of connections in all pools associated with the process or AppDomain.

The NumberOfReclaimedConnections. This counter is new to ADO.NET 2.0. It represents the number of emancipated connections. Emancipated connections occur when the object that owns the connection goes out of scope. ADO.NET 2.0 reclaims them, when the pool runs out of connections or during normal thread cleanup.

The NumberOfStasisConnections. This counter is also new in ADO.NET 2.0. These would include connections that are enlisted in distributed transactions or are otherwise unavailable.