I have an SSIS package that reads data from Oracle and inserts it into SQL Server.
The SQL Server is clustered (node1, node2) but it doesn't have MSDTC. The package runs fine without problems.
I have read that if you are using SSIS package then MSDTC is a must when configuring SQL Server cluster. But I am not using it and still package is working fine so I wanted to ask what's the use of MSDTC? How is my package working without it?
Mayday! Mayday!
A distress signal is being sent out to all past, present and future Gurus!
We need more of your awesomeness!
The TechNet Guru Competitions have become BIG news within Microsoft circles, drawing in more and more departments. Over the last year or so, we have found new and old talent emerging from the community. This is your chance to come out of the shadows of daily grind and take your rightful place in the sun. Come bask in the glory we bestow upon our winners. Build a reputation and promote your own awesomeness to the world (and potential employers).
So bring us your snippets, black holes and revelations. Enlighten us with your factoids and work-arounds. Thrill us with your nifty walk-throughs, overviews and analysis.
Not forgetting Star Wars day!
May the 4th be with you!
All you have to do is add an article to TechNet Wiki from your own specialist field. Something that fits into one of the categories listed on the submissions page. Copy in your own blog posts, a forum solution, a white paper, or just something you had to solve for your own day's work today.
Drop us some nifty knowledge, or superb snippets, and become MICROSOFT TECHNOLOGY GURU OF THE MONTH!
This is an official Microsoft TechNet recognition, where people such as yourselves can truly get noticed!
HOW TO WIN
1) Please copy over your Microsoft technical solutions and revelations toTechNet Wiki.
2) Add a link to it on THIS WIKI COMPETITION PAGE (so we know you've contributed)
3) Every month, we will highlight your contributions, and select a "Guru of the Month" in each technology.
If you win, we will sing your praises in blogs and forums, similar to the weekly contributor awards. Once "on our radar" and making your mark, you will probably be interviewed for your greatness, and maybe eventually even invited into other inner TechNet/MSDN circles!
Winning this award in your favoured technology will help us learn the active members in each community.
Feel free to ask any questions below.
More about TechNet Guru Awards
#PEJL
Got any nice code? If you invest time in coding an elegant, novel or impressive answer on MSDN forums, why not copy it over to the one and onlyTechNet Wiki, for future generations to benefit from! You'll never get archived again!
If you are a member of any user groups, please make sure you list them in the
Microsoft User Groups Portal. Microsoft are trying to help promote your groups, and collating them here is the first step.
hi all,
i have a few DBF files in different folders and I need to import these files into a SQL Server database.
The files are present in different folders. There is one main folder for each customer and under that, there are several subfolders. The structure and name of the folder/files is same for all the customers(except for the fact that the main folder goes by the name of the customer).
i designed a package to pull data for one customer but i want to make it to work dynamically for other customers by changing the connection dynamically and using a for each loop. The name of each customer and a path to their main folder is stored in a SQL Server table. any idea how to do this?
I have an SSIS package that is taking data from a table, performing some derived column tasks and dumping the data into another table. All on the same database on the same server.
When I run the package in BIDS it completes in 30 mins.
When I run it in a command prompt using DTEXEC it completes in 1 hour.
When I schedule the package to run in SQL server agent, it takes 1 hour to complete. I've scheduled the package source as SQL Server, File system, and SSIS Package Store, and all three complete in 60 seconds. I've also tried changing the run as account from the sql server agent service account to a proxy account. I even tried restarting services and rebooting the machine. I'm beginning to think there is a bug with SQL Agent where it takes longer to execute SSIS packages.
My server is x64 with Windows Server 2008 R2 Ent. x64
SQL version: Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Sep 16 2010 19:43:16 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
The packages are also x64.
Can anyone please help figure out why the scheduled package is running so slow?
Hi,
I had the SSIS packages (ETL job) working fine for a long time and then we moved the server/machine and ETL job keeps failing.
The ETL job run number of packages. The ETL job fails for the first run then I set the retires and it works in 2nd or 3rd try on the ETL job but it fails daily for the first run where DTexec.exe crash (log pasted below)
Server: Windows 2008 R2
SQL Server: SQL Server 2008 R2
RAM 64 GB
CPU cores 8
we had the similar specs on previous machine and ETL job worked fine. Only difference is we have 2 SQL server instances now on same machine.
I am suspecting it's an issue with ETL packages but why it was working fine before for a long time and after machine move it keeps failing.
Any thoughts?
Version=1
EventType=APPCRASH
EventTime=130432662277734721
ReportType=2
Consent=1
ReportIdentifier=f2ff88b6-cfc3-11e3-babd-005056997b14
IntegratorReportIdentifier=f2ff88b5-cfc3-11e3-babd-005056997b14
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=DTExec.exe
Sig[1].Name=Application Version
Sig[1].Value=2009.100.4263.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5036ba73
Sig[3].Name=Fault Module Name
Sig[3].Value=DTSPipeline.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=2009.100.4263.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5036ba53
Sig[6].Name=Exception Code
Sig[6].Value=40000015
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000a33c5
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.274.10
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3081
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=7c29
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=7c290b53eb7940378e43b699d1de1f07
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=199e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=199e6470d3145d6303fbe30033cf7038
UI[2]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Data Transformation Services Execution Utility stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\MSVCR80.dll
LoadedModule[9]=C:\Windows\system32\USER32.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\LPK.dll
LoadedModule[12]=C:\Windows\system32\USP10.dll
LoadedModule[13]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[14]=C:\Windows\system32\ole32.dll
LoadedModule[15]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEParse.dll
LoadedModule[16]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\MSVCP80.dll
LoadedModule[17]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEPkg.dll
LoadedModule[18]=C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_8a1dd9552ed7f8d8\ATL80.DLL
LoadedModule[19]=C:\Windows\system32\PSAPI.DLL
LoadedModule[20]=C:\Windows\system32\VERSION.dll
LoadedModule[21]=C:\Windows\system32\IMM32.DLL
LoadedModule[22]=C:\Windows\system32\MSCTF.dll
LoadedModule[23]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[24]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[25]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTS.dll
LoadedModule[26]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[27]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\dtsmsg100.dll
LoadedModule[28]=C:\Windows\system32\CRYPT32.dll
LoadedModule[29]=C:\Windows\system32\MSASN1.dll
LoadedModule[30]=C:\Windows\system32\SXS.DLL
LoadedModule[31]=C:\Windows\System32\msxml6.dll
LoadedModule[32]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[33]=C:\Windows\system32\rsaenh.dll
LoadedModule[34]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[35]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DtsConn.dll
LoadedModule[36]=C:\Windows\system32\SHELL32.dll
LoadedModule[37]=C:\Windows\system32\mscoree.dll
LoadedModule[38]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[39]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[40]=C:\Windows\system32\profapi.dll
LoadedModule[41]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\88744044294787b99dd4a8704ab75a79\mscorlib.ni.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\af0a0b96a02f9925eb84392ee65a5cfa\System.ni.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\40937910f60adedfb214d89b989f929d\Microsoft.SqlServer.ManagedDTS.ni.dll
LoadedModule[44]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\f82fe091649105fb4de1195cb9da7438\Microsoft.SqlServer.DTSRuntimeWrap.ni.dll
LoadedModule[45]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\77e0f983055ea695867ca69afaecda79\Microsoft.SqlServer.SQLTask.ni.dll
LoadedModule[46]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\3975acf49313ceea1280da91f0383480\System.Xml.ni.dll
LoadedModule[47]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\80c6801f36d7c3e891323f6b53dccbcc\Microsoft.SqlServer.Msxml6_interop.ni.dll
LoadedModule[48]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\ExecPackageTask.dll
LoadedModule[49]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\Resources\1033\dtsmsg100.rll
LoadedModule[50]=C:\Windows\system32\urlmon.dll
LoadedModule[51]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[52]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[53]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[54]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[55]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[56]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[57]=C:\Windows\system32\normaliz.DLL
LoadedModule[58]=C:\Windows\system32\iertutil.dll
LoadedModule[59]=C:\Windows\system32\WININET.dll
LoadedModule[60]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[61]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTSComExprEval.dll
LoadedModule[62]=C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll
LoadedModule[63]=C:\Program Files\Microsoft SQL Server\100\Shared\SQLBoot.dll
LoadedModule[64]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\c9743c9d2ac43664c43d9a0b3fbb5548\Microsoft.SqlServer.DtsMsg.ni.dll
LoadedModule[65]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\5ef353725aeb5af35fb49c3f300c38b3\Microsoft.SqlServer.SQLTaskConnectionsWrap.ni.dll
LoadedModule[66]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\52f53ccfcc9570f1fd13f63d0a640e81\Microsoft.SqlServer.BatchParser.ni.dll
LoadedModule[67]=C:\Windows\assembly\GAC_64\Microsoft.SqlServer.BatchParser\10.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.BatchParser.dll
LoadedModule[68]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\msvcm80.dll
LoadedModule[69]=C:\Program Files\Common Files\System\Ole DB\oledb32.dll
LoadedModule[70]=C:\Windows\system32\MSDART.DLL
LoadedModule[71]=C:\Windows\system32\bcrypt.dll
LoadedModule[72]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
LoadedModule[73]=C:\Program Files\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[74]=C:\Windows\system32\comsvcs.dll
LoadedModule[75]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[76]=C:\Windows\system32\sqlncli10.dll
LoadedModule[77]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
LoadedModule[78]=C:\Windows\system32\COMDLG32.dll
LoadedModule[79]=C:\Windows\system32\NETAPI32.dll
LoadedModule[80]=C:\Windows\system32\netutils.dll
LoadedModule[81]=C:\Windows\system32\srvcli.dll
LoadedModule[82]=C:\Windows\system32\wkscli.dll
LoadedModule[83]=C:\Windows\system32\WS2_32.dll
LoadedModule[84]=C:\Windows\system32\NSI.dll
LoadedModule[85]=C:\Windows\system32\1033\SQLNCLIR10.RLL
LoadedModule[86]=C:\Windows\system32\secur32.dll
LoadedModule[87]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[88]=C:\Windows\system32\credssp.dll
LoadedModule[89]=C:\Windows\system32\kerberos.DLL
LoadedModule[90]=C:\Windows\system32\cryptdll.dll
LoadedModule[91]=C:\Windows\system32\msv1_0.DLL
LoadedModule[92]=C:\Windows\system32\ntdsapi.dll
LoadedModule[93]=C:\Windows\system32\LOGONCLI.DLL
LoadedModule[94]=C:\Windows\system32\security.dll
LoadedModule[95]=C:\Windows\system32\schannel.DLL
LoadedModule[96]=C:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll
LoadedModule[97]=C:\Windows\system32\mswsock.dll
LoadedModule[98]=C:\Windows\System32\wshtcpip.dll
LoadedModule[99]=C:\Windows\System32\wship6.dll
LoadedModule[100]=C:\Windows\system32\DNSAPI.dll
LoadedModule[101]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[102]=C:\Windows\system32\WINNSI.DLL
LoadedModule[103]=C:\Windows\system32\rasadhlp.dll
LoadedModule[104]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[105]=C:\Windows\system32\ncrypt.dll
LoadedModule[106]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\SQLTaskConnections.dll
LoadedModule[107]=C:\Windows\system32\ODBC32.dll
LoadedModule[108]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\BatchParser.dll
LoadedModule[109]=C:\Windows\system32\odbcint.dll
LoadedModule[110]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[111]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Data\5e957216f11830cbc49b4b30314e0e10\System.Data.ni.dll
LoadedModule[112]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[113]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.AddIn\b3b4d44d80055c9e96909f153ff92fbc\System.AddIn.ni.dll
LoadedModule[114]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\5388ebc8e600ad2542d8afbef9559944\Microsoft.SqlServer.ScriptTask.ni.dll
LoadedModule[115]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\492ba64d2cb55aa910114c85c2327821\Microsoft.SqlServer.VSTAScriptingLib.ni.dll
LoadedModule[116]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.VisualStu#\f3ab3bf00723d757396110ac3dc57a6d\Microsoft.VisualStudio.Tools.Applications.DesignTime.v9.0.ni.dll
LoadedModule[117]=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTSPipeline.dll
LoadedModule[118]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\06aaaec444077ab8248b28b0bdf2c3b2\Microsoft.SqlServer.PipelineXML.ni.dll
LoadedModule[119]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\3dce1dfa4ea9d165471de3b83b82893c\Microsoft.SqlServer.SqlTDiagM.ni.dll
LoadedModule[120]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\4f58550979ad960c616b557266fbc5d0\Microsoft.SqlServer.Diagnostics.STrace.ni.dll
LoadedModule[121]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\fed86e49fe95761085bf287f901f5b53\System.Configuration.ni.dll
LoadedModule[122]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\6f12b249b9bd278ddc1a5ea48fb1221e\Microsoft.SqlServer.DTSPipelineWrap.ni.dll
LoadedModule[123]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\OleDbSrc.dll
LoadedModule[124]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\OleDbDest.dll
LoadedModule[125]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxDerived.dll
LoadedModule[126]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxRowCount.dll
LoadedModule[127]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\CommandDest.dll
LoadedModule[128]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxSplit.dll
LoadedModule[129]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxMergeJoin.dll
LoadedModule[130]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxSort.dll
LoadedModule[131]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxDataConvert.dll
LoadedModule[132]=C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.SqlServer#\78f11d2ba751edf529c28ca8b012d697\Microsoft.SqlServer.PipelineHost.ni.dll
LoadedModule[133]=C:\Windows\assembly\GAC_MSIL\KimballMethodSCD100\1.0.0.0__8b0551303405e96c\KimballMethodSCD100.dll
LoadedModule[134]=C:\Windows\assembly\GAC_MSIL\SSISComponentUtilities\1.0.0.0__8b0551303405e96c\SSISComponentUtilities.dll
LoadedModule[135]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\868d117286ad259249f31d3fe813d39a\System.Drawing.ni.dll
LoadedModule[136]=C:\Windows\assembly\NativeImages_v2.0.50727_64\CustomMarshalers\98e9b163a01ce659f1bb3d7ee15be7bf\CustomMarshalers.ni.dll
LoadedModule[137]=C:\Windows\assembly\GAC_64\CustomMarshalers\2.0.0.0__b03f5f7f11d50a3a\CustomMarshalers.dll
LoadedModule[138]=C:\Windows\system32\apphelp.dll
LoadedModule[139]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxLookup.dll
LoadedModule[140]=C:\Program Files\Microsoft SQL Server\100\DTS\PipelineComponents\TxUnionAll.dll
LoadedModule[141]=C:\Windows\assembly\NativeImages_v2.0.50727_64\EnvDTE\4a689bff8b507e736eea8e5b2b21d42a\EnvDTE.ni.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Data Transformation Services Execution Utility
AppPath=C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
Hi,
source file type is .csv. I am using executeprocess task to download the source file..its thrown error by the executeprocesstassk and also through command prompt. all arguments are sitting properly. I checked each and every arguments.
with the same executables i can downloaded few of the flat files.
But for this only I am facing an issue.actually How i am getting an issue is.
for eg flat file having 5 headers. like procid,procname,proccast,procsale,updateddate.
while running the task/from cmd prompt it 'll work fine for procid,procname,proccast. i mean to say getting data. but not getting rest of the 2 fields.
output: procid,procname,proccast,procsale,updateddate only hearders without data.
for some times it's throws an error below if i'll take few of the fields like procid,procname,proccast,procsale.
Error: I cant seem to download the file, please check the filename and URL. Web
Exception Error:
System.Net.WebException: The remote server returned an error: (500) Internal Ser
ver Error.
at System.Net.WebClient.File(Uri address, String fileName)
at System.Net.WebClient.File(String address, String fileName)
at Script.Program.Main(String[] args)
but when i checked individually all fields are having data & excution is success.
Hope for the quick solution.
Thanks
I have 3 components as below
1. Execute Sql Task ---> It will fetch The data from Database using ConnectionType "OLEDB" ("Full Result Set" its returning) and Store it in the Variable as below,
"ConfigDetails" "Scope --> Package" "Type - Object".
2. Script Task (First) ----> Here "ConfigDetails" Variable is part of "ReadOnlyVariables", So i am accessing this varaible and populating data from it in the Data Table object as below,
OleDbDataAdapter configAdapter = new OleDbDataAdapter();
DataTable dtConfigurationList = new DataTable();
object config = Dts.Variables["ConfigDetails"].Value;
configAdapter.Fill(dtConfigurationList, config);
So here i am successfull in populating data in the data table .
3. Script Task (Second)--> Same thig i am doing in second script task also as "First"
Here "ConfigDetails" Variable is part of "ReadOnlyVariables", So i am accessing this varaible and populating data from it in the Data Table object as below,
OleDbDataAdapter configAdapter = new OleDbDataAdapter();
DataTable dtConfigurationList = new DataTable();
object config = Dts.Variables["ConfigDetails"].Value;
configAdapter.Fill(dtConfigurationList, config);
So here it will execute successfully without any error. But no data is there in the data table .
If i skip first script task, second script task is able to populate the data. But i am not righting any code to nullify the object and its part of "Read Only Varaibles."
So please help me what i am doing wrong.
configAdapter.Fill(dtConfigurationList, config);
Could please any one explain with simple example
Thanks
Could you please any one explain with simple example
Thanks
I have a column of datatype date in a table in sql server..for few rows i want to update their value to 'In Hold' in that column.
How to write a update statement to insert string value to date datatype field???
Actually i am trying to update this using SSIS.
Can anyone please help!!!!!
Thanks in advance!!!
Hello,
Need to generate first data from stored procedure and the save it to an excel file and then send mail with the same excel file.
So am searching for the best way so that i could do all process in a single task with daily or monthly schedule.
As per my understanding, we could it via SSIS and by sql server using sp_send_dbmail.
But i have to generate excel file first by stored procedure and then end it by mail.
So please suggest the best way to accomplish all task in a single task.
Thanks
Ajay
Hi,
I have access database where I have couple of hundred tables and I am trying to import all the tables to SQL server using SSIS but in OLEDB source editor it's showing only 7 to 8 tables instead all the hundred's of tables.
Please let me know if anyone knows the solution.
Thank you
S
srinivas
I created an 2008 SSIS package which uses a Connection Manger connection to an iSeries host. It uses an IBM i Access for Windows OLE DB driver - IBMDA400. (OLD DB Provider: IBM DB2 for i IBMDA400 OLE DB Provider). The documentation on the i Access OLE DB said to use SSL=TRUE in the connection string for SSL. So I added it. I see it in the dtsx. I deploy the package to MSDB and when I right click on the package to Run Package, I do not see the SSL=TRUE anywhere in the Execute Package Utility. Want to verify that even though I do not see it in the EPU, that it is in the package. Is there a way to view the syssispackages.packagedata is a format that is readable? Is there a way to verify that it is using SSL?
SSIS - Execute Package Utility, DB2Source Connection String
===========================================================
Data Source=develop;User ID=GROSSNICKB;Initial Catalog=;Provider=IBMDA400.DataSource.1;
dtsx
====
<DTS:Property DTS:Name="DelayValidation">0</DTS:Property>
<DTS:Property DTS:Name="ObjectName">DB2Source</DTS:Property>
<DTS:Property DTS:Name="DTSID">{817C7D72-C2CC-49B2-8B6A-064DCC531999}</DTS:Property>
<DTS:Property DTS:Name="Description"></DTS:Property>
<DTS:Property DTS:Name="CreationName">OLEDB</DTS:Property><DTS:ObjectData><DTS:ConnectionManager>
<DTS:Property DTS:Name="Retain">0</DTS:Property>
<DTS:Property DTS:Name="ConnectionString">Data Source=develop;User ID=THEBRENDA;Provider=IBMDA400.DataSource.1;Persist Security Info=False;SSL=TRUE;</DTS:Property></DTS:ConnectionManager></DTS:ObjectData></DTS:ConnectionManager>
=False;SSL=TRUE;</DTS:Property></DTS:ConnectionManager></DTS:ObjectData></DTS:ConnectionManager>
Problem: An Excel file (XLSX) dynamically created by a SQL Task cannot be opened via Excel. The task succeeds, but when you try to open the workbook in Excel you get the fillowing error message: Excel cannot open the file 'myfile.xlsx" because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file.
Observations:
1. If the Excel file (xlsx) is created manually in Excel, then the SQL Task has no problem creating table (new worksheets) in the xlsx (so the "CREATE TABLE" statement works fine)
2. If I adjust the connection and task to work with Excel 97-2003 (xls) format then the approach works perfectly
3. The execution results show success of the SQL Task, but there are two warning messages. These same warnings appear when the SQL Task creates a new table (worksheet) successfully in a workbook (xlsx) which was created manually in Excel (and is not corrupt).
Messages as follows:
Warning: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Warning: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
SSIS Details:
1. ConnectionString: "Data Source=" + @[User::ExcelFileFullPathName] + ";Provider=Microsoft.ACE.OLEDB.12.0;Extended Properties=\"Excel 12.0;HDR=YES\";"
2. SQLStatementSource (from SQL Task):
"CREATE TABLE `" + @[User::cfgExcelTransformTableName] + "` (
`Number` VarChar(15),
`Name` VarChar(252),
`Site/Organization` VarChar(255),
`Priority` VarChar(255),
`Description` LongText,
`Status` VarChar(255),
`Start Date` VarChar(255),
`End Date` VarChar(255),
`Category` VarChar(255),
`Project Contact` VarChar(255),
`Sponsor` VarChar(255),
`Funding Source` VarChar(255),
`Partner` LongText,
`Budget` Double,
`Allocated Funding by Source` VarChar(255),
`Allocated Funding` Double,
`Expended Funding` Double,
`Habitat Type` VarChar(255),
`Limiting Factors` VarChar(255),
`Primary Species Benefiting` VarChar(255),
`Secondary Species Benefiting` VarChar(255),
`Current Project Status` VarChar(255),
`Activity Type(s)` LongText
)
"
3. Run64BitRuntime = False
Hardware/Software Details:
1. Windows 7 Ultimate (64 bit)
2. Excel Version 14.0.4760.1000 (64 bit)
3. Visual Studio 2008
4. Office 2007 Data Connectivity Components:
http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=en
http://support.microsoft.com/kb/2837964/en-us addresses this issue indicating SQL 2012 SP1 with CU4 resolves the issue, it does not. It does appear to remove the random failure, but does not resolve the issue below.
A parent package is run from the SQL Server Agent which calls many child packages via a ForEach loop. The child packages read from a flat file and load to SQL. The incoming files are generated by external clients, many using a manual creation process, files not in the correct format occur. When the flat file connection manager in the child package attempts to up an incorrectly formatted file the Unexpected Termination occurs. For 24 months this same set of packages has run in SQL 2008 R2, when encountering an incorrcetly formatted file an error is emailed and logged, the child package fails, returning control to the parent package which continues to process the remaining file locations.
No errors are logged in SQL 2012 or windows application log when the Unexpected Termination occurs. What can be done to allow the parent package to continue to function?
I need to perform a left outer join in SSIS. I am using merge join between an excel source and a oledb source.But it is not yielding is same results.
IS Left outer join in Merge Join transformation is same as left outer join in left outer join in SQL Server??
Please help!!!!
Thanks in Advance!!!!
We have a customer where our SQL Agent jobs run SSIS packages every hour at 40 minutes past the hour. When our steps were configured to run with 64-bit dtexec the jobs failed 30-40% of the time they were executed. In the job history we see a message like this:
Executed as user: SERVER\USERNAME. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights
reserved. Started: 1:35:00 PM. The return value was unknown. The process exit code was -2146233082. The step failed.
The exit code varies, though it is often as shown above.
In the Application event log we see an Error with the source = Application Error like this:
Faulting application name: DTExec.exe, version: 2009.100.4000.0, time stamp: 0x4fec7ecd
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
Exception code: 0xc0000374
Fault offset: 0x00000000000c4102
Faulting process id: 0x49ec
Faulting application start time: 0x01cf5810f1324095
Faulting application path: C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 31f927ca-c404-11e3-b7b9-005056a55353
Sometimes the reported faulting module name is mscorwks.dll, version: 2.0.50727.5477, rather than ntdll.dll.
After changing all the SSIS steps in the job to use the 32-bit run time the rate of failures dropped significantly to about 10% or a bit less. The same symptoms remain, though, with intermittent job failures associated always with a dtexec.exe crash and a message in the application event log like this:
Faulting application name: dtexec.exe, version: 2009.100.4000.0, time stamp: 0x4fec7fd7
Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb1072
Exception code: 0xc0000374
Fault offset: 0x000ce753
Faulting process id: 0x40ac
Faulting application start time: 0x01cf653a7776640e
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\dtexec.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b7db79b2-d12d-11e3-b7b9-005056a55353
I have run DebugDiag 2.0 on the WER hdmp files that get created each time dtexec crashes and I have not had any luck getting any idea what might be causing these crashes through that process. I could use some help figuring out the root cause. The server is running Windows 2008 R2 on a VMWare virtual machine. It is configured with 4 cores and 8gb memory.
There are custom tasks involved in these SSIS packages but nothing in the DebugDiag crash analysis output seems to be pointing at that custom code as far as I can tell.
Re-running the failed job usually results in a successful execution.
Any help would be greatly appreciated.
John Hansen
I want to copy the dynamic files end of every month from one location to another.
File format : \\test\data\<databasename>_<backup>_<year>_<month>_<day>_<system generated number>_<system_generated_number>.bak
I went through many articles to use file system task to move files. There are daily backup which are already present in the same location. I don't want to copy those files in the same location. I want to copy only EOM file created in the previous month dated as "_2014_04_30_".
Any help here would be highly appreciated.
-kccrga http://dbatrend.blogspot.com.au/
