I am playing around with creating packages using C#. One major problem I have run into is controlling the location of the tasks I create in the package. I have found no way to access any properties to set this. Does anyone know how to do this?
View 4 RepliesI am trying to code a package that runs a transferdatabasetask with the following code
Dim package As New Package()
package.PackageType = DTSPackageType.DTSDesigner90
package.Name = "transfer db task"
package.Description = "transfer db task"
package.CreatorComputerName = System.Environment.MachineName
package.CreatorName = System.Environment.UserName
Dim dest As ConnectionManager = package.Connections.Add("OLEDB")
dest.Name = "Dest"
dest.ConnectionString = "Data Source=NSW97V9F1SNSW97V9F1S;Initial Catalog=RGTemp;User Id=rgTest;Password=12345"
'dest.ConnectionString = "SqlServerName=PDNCNLNJ1SSQLSERVER2005;UseWindowsAuthentication=True;UserName=sa;"
Dim source As ConnectionManager = package.Connections.Add("OLEDB")
source.Name = "Source"
source.ConnectionString = "Data Source=NSW97V9F1SNSW97V9F1S;Initial Catalog=RGTemp;User Id=rgTest;Password=12345"
'source.ConnectionString = "SqlServerName=NSW97V9F1SNSW97V9F1S;UseWindowsAuthentication=True;UserName=;"
Dim th As TaskHost = TryCast(package.Executables.Add("STOCK:TransferDatabaseTask"), TaskHost)
th.Name = "transfer db task"
th.Description = "The transfer task"
th.Properties("Action").SetValue(th, 0) '0: copy
th.Properties("Method").SetValue(th, 1) '1: destination online
th.Properties("DestinationConnection").SetValue(th, dest.ID)
th.Properties("DestinationDatabaseFiles").SetValue(th, "rgTemp1.mdf,C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATA,'';rgTemp1_log.ldf,C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATA,''")
'th.Properties("DestinationDatabaseFiles").SetValue(th, "C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATA
gTemp1.mdf;C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATA
gTemp1_log.ldf")
th.Properties("DestinationDatabaseName").SetValue(th, "RGTemp1")
th.Properties("DestinationOverwrite").SetValue(th, True)
th.Properties("ReattachSourceDatabase").SetValue(th, False)
th.Properties("SourceConnection").SetValue(th, source.ID)
th.Properties("SourceDatabaseFiles").SetValue(th, "'rgTemp.mdf','C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATA','';'rgTemp_log.ldf','C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATA',''")
MsgBox(th.Properties("SourceDatabaseFiles").GetValue(th).ToString)
MsgBox(th.Properties("DestinationDatabaseFiles").GetValue(th).ToString)
th.Properties("SourceDatabaseName").SetValue(th, "RGTemp")
Dim status As DTSExecResult = package.Validate(Nothing, Nothing, Nothing, Nothing)
' If the package validated successfully, then execute it.
If status = DTSExecResult.Success Then
' Execute the package
Dim result As DTSExecResult = package.Execute(Nothing, Nothing, Nothing, Nothing, Nothing)
End If
'Dts.TaskResult = Dts.Results.Success
End Sub
The problem is that the package validation fails and the 'execute' statement never runs. the two message boxes report zero length strings in the source and destination files properties. It seems that the hard coded filenames that I have provided are not correct.
Can anyone shed any light on what is wrong here:
regards
Ray
I've run into a problem with SSIS packages wherein tasks that write or copy files, or create or delete directories, quit execution without any hint of an error nor a failure message, when called from an ASP.NET 2.0 application running on any other machine than the one where the package was created from. By all indications it appeared to be an identity/permissions problem.
Our application involves a separate web server and database server. Both have SQL Server 2005 installed, but the application server originally only had Integration services. The packages are file system-deployed on the application server, and are called using Microsoft.SqlServer.Dts.Runtime methods. For all packages that involve file system tasks, the above problem occurs.
When the above packages are run using the command prompt (either DTEXEC or DTEXECUI) the packages execute just fine. This is expected since we are using an administrative account. However when a ShellExecute of the same command is called from ASP.NET, the same problem occurs.
I've tried giving administrative permissions to the ASPNET worker process user to no avail.
I have likewise attempted to use the SQL Server Agent job approach but that approach might not be acceptable for our clients since it means installing SQL Server 2005 Database services on the application server.
I have read the relevant threads in this forum, namely http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1044739&SiteID=1 and http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=927084&SiteID=1 but failed to find any solution appropriate for our set up.
Anybody got any idea on how to go about this?
We manage some SSIS servers, which has only SSIS and SSIS tools installed on them and not the sql server DB.
SSIS packages and configuration files are deployed on a NAS. We run the SSIS packages through DTEXEC by logging in to the server.
We want to allow developers to run their packages on their own on the server, but at the same time we dont want to give them physical access on the server i.e we do not want to add them into RDP users list on server properties. We want them to allow running their packages remotely on the server.
One way We could think of is by using powershell remoting and we are working on that. But is there any other way or any tool already present for the same.
Hello,
Is there a way is a script task or via a procedural expression to tell if a package is going to fail because of an error?
This would be used to fire something which should occure if the max number of errors/error severity to fail the package had been reached
Thanks
Paul
in the following i'm trying to create a sqldatasource and link it to a drop down list, is it possible?
Protected Sub DDL_Selections_SelectedIndexChanged1(ByVal sender As Object, ByVal e As System.EventArgs) Handles DDL_Selections.SelectedIndexChanged
If Me.DDL_Selections.SelectedItem.Text = "All" ThenDBconn = New System.Data.SqlClient.SqlConnection("Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory|Database.mdf;Integrated Security=True;User Instance=True")
DBcmd = New System.Data.SqlClient.SqlCommand("SELECT [DateEntered], [From], [To], [Company], [Catagory], [Client], [Description], [TotalHours] FROM [JcpowersJobs] ORDER BY [From]", DBconn)DBSDA = New System.Data.SqlClient.SqlDataAdapter("SELECT [DateEntered], [From], [To], [Company], [Catagory], [Client], [Description], [TotalHours] FROM [JcpowersJobs] ORDER BY [From]", DBconn)
Me.DDL_Selections.DataSourceID = "DBSDA"
End If
End Sub
Hi
How to implement the SSIS package. My requirement is to send a mail to user when the new user account created by admin by using SSIS concept. Kindly post your ideas with sample codings.
Kamal..
I am relatively new to this. I am trying to create a SSIS package that loops through several SQL tables. The first table is results_C01 and the last table is results_C18. They are in the same database. The number of tables will be increasing over time. I would like to perform a series of the same SQL tasks on these tables. My thought was to utilize a For Loop and imbed the SQL tasks within the For Loop. The SQL task would utilize a variable for the table name that would increment from results_C01 to results_C18 as it cycled through the For Loop.
I am able to create a For Loop with a variable, but I am not able to get the variable from the For Loop to equal and increment from results_C01 to results_C18. Secondly, I am not able to create an SQL task that utilizes a variable for a table name. I am really stuck.
hello,
I'm new to this SSIS package creation thing and I'm a little stuck. I have to create a SSIS project and create packages that drop - create a database, then create either 1 or 3 different packages that use a config file for input on dates to run and return data. My question is:
1) how can I get a package to read a config file?
2) do i need to create 3 seperate configs files for each different packages?
3) How can I pass in parameters to the config file or allow the config file allow for parameters to be passed in? meaning: I need to allow my config files run between dates I entered in.
I'm totally new to this SSIS thing, I'm a .NET developer and never done this stuff before in my life so I'm not really sure how to do most of this stuff within the VS 05 IDE for the SSIS package creations.
Hi All, i've been reading this article http://rafael-salas.blogspot.com/2006/12/import-header-line-tables-_116683388696570741.html
in regards to creating an excel spreadsheet dynamically in SQL Server 2005 SSIS. However, i'm constantly getting an where the tab is created but not being populated. Can somebody post up a clearer example?
The problem I'm trying to solve is to automate the export of a query onto a new dynamic spreadsheet each time I run this SSIS package.
Any help would be greatly appreciated.
Thank you.
I have a requirement where in i need to create a Database dynamically in SSIS, Database name is given in table.
View 3 Replies View RelatedI'm trying to create an SSIS package that will do a straight data copy between databases. The problem is that the underlying schema of the origin may change and the requirement is that the transfer be table driven. i.e. the tables that are copied are listed in a table and there should be no human intervention when the schema changes.
I'm moving data between SQL Server and SQL Azure, so backup and restore doesn't work. Has to be an SSIS package.
What's the best way to deal with a changing schema in an SSIS package? Can I delete and rewrite the underlying XML for any tables that change? Do I need to do it programmatically with C#? Do I need to create the package from scratch each time?
I've been searching everywhere for a solution to this problem and no answers exist anywhere. When I try to create a new maintenance plan I get the following error. I've been told it may be related to SSIS but nobody has a solution. How do I fix this issue so I can create a maintenance plan.
Exception has been thrown by the target of an invocation. (mscorlib)
ADDITIONAL INFORMATION:
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
An OLE DB error 0x80004005 (Client unable to establish connection) occurred while enumerating packages. A SQL statement was issued
and failed.
I need to create a DB dynamically in the Server from the SSIS only....
How to implement this....
I am facing one process related issue.
I have one task in which i have to collect lots of .txt file having ## delimiter my requirement is to convert the delimiter from ## to comma and save the new file with .dat extension in different folder.
I have done all required process and run the application which should flow like collect source .txt file do Script component processing and create new .dat file with processed data in Data Flow task, but in my Task the Source and Destination start on same time and process start after words which cause empty file or some time a.txt file data stored in b.dat file where as a.dat file is completely empty.
The process should flow in sequence but behavior is totally against the process, i am using Foreach Loop Container for pick up each file.
Hi ,
How to INsert and Update Large Amount of Records (4 Lacs) into Destination Table Through Business Intelligence Studio Using SSIS Pacakge .How to Achieve this .i tryed with left outer join & conditional split but the problem its not able to insert & update records simultaneously . can any one give me a sample .
Thanks & Regards
Jeyakumar.M
Hi,
Is there a way to reuse existing Configuration Files in SSIS Packages?
I have two packages with the same connection managers, properties and variables.
I want to reuse the Config file of the 1st package in the second one. While building the packages it gives error like
“Config file already exists cannot recreate”.
Hi All,
I have created SSIS (.dtsx) files and have stored in different servers.
Now my query is I want to move all dtsx files from filesystem to Sqlserver2005 database how should i do it.
Please help
Regards
Hassan
I need to create the ssis package in business intelligence developement studio i am need to sqlserver 2005.When i opened the BID studio i am not able to see the integration services packages type..
Please help the steps to design the package.
I have experience of using the 2000 in dts designer mode.
Thnks for your help in advance.
Hi,
iam New to Packages. So Please give me the guidelines to Learn Packages.
Thanks for Advance
Hi,
I upgraded to Microsoft SQL Server 2005 Service Pack 2 and now when I run the master SSIS package( that has several packages in it), all the packages run twice.
After removing SP2, they work fine. Any ideas how to make this work with SP2?
I am writing a vb application that is supposed to let the users set the connection string for the datasources in the package. After new connection strings are entered the application is supposed to run 8 packages in a certain order, but I haven't been able to set a new connection string successfully. Is there a way to programmatically modify the connection string of a package's datasource? (the packages are moving data from a D3 database to sql server 2005)
Here is what I have tried so far:
A.
Dim pkgLocation As String
Dim app As Application = New Application()
pkgLocation = "c:Package1.dtsx"
Dim pkg As Package = app.LoadPackage(pkgLocation, Nothing)
Dim myConns As Connections = pkg.Connections
MessageBox.Show(myConns(0).ID.ToString)
Dim myConnMgr As ConnectionManager = myConns(0)
Dim connProperties As DtsProperties = myConnMgr.Properties
connProperties(0).SetValue(myConnMgr, "notsupposed=towork;")
MessageBox.Show(myConnMgr.ConnectionString)
B.
ConMgr = p.Connections.Add("OLEDB")
ConMgr.ConnectionString = "Provider=SQLNCLI.1;Data Source=192.168.0.233; User ID=sa; Initial Catalog=Rmt_New"
ConMgr.Name = "SqlDatabase"
ConMgr.Description = "Sql Connection"
Any help would appreciated.
I am connecting to a DB2 mainframe to pull data into SQL 2005. Very simple import. SSIS package works fine on 32 bit. However, once deployed to the 64 bit machine, I get "invalid product license" on the Acquire Connection method.
I've worked with IBM support. I have the correct version of the DB2 Connect client installed. The license is there and in the right place. I can connect to the mainframe from the 64 bit server using the DB2 client tools. I just can't seem to execute the package from Integration Services or run a job in SQL Server that executes the package.
According to BOL, the package should automatically detect the 64 client I installed. It and the 32 bit client I developed with share the same name/id.
Am I missing something? Any hints?
Where are SSIS packages stored and how can I see them in SQL Server Management studio?
View 6 Replies View RelatedI read in Kirk Haselden's book "Microsoft SQL Server 2005 Integration Services" that if SQL Serfver 2005 and 2000 are installed on the same machine as seperate instances then you can view the SQL Server 2000 DTS packages in 2005 Management Studio under the Management tree, Legacy, Data Transformation Services node.
But in my case, I am not able to see DTS packages in Management Studio. Is there a property or a setting that we need to configure for that?
Thanks.
I'm still new to SSIS packages and I'm NOT a developer. I am in the process of doing preliminary/prepatory work for migrating our SQL 2000 platforms to SQL 2005.
I am having a REAL headache with migrating/moving DTS packages from SQL 2000 to SQL 2005. Here are things that I know :
1. I know that some packages cannot be migrated due to ActiveX issues and other issues. Fine.
2. I know that I can install DTS backwards compatibility components on the server in order to be able to edit the DTS packages using a SQL 2000 DTS GUI. Fine.
3. I know that I can use the Migration wizard to migrate packages (and that some of them can't be migrated this way). Fine.
Here's what I don't know/or am conjecturing:
1. In a clustered environment, I have to edit the <%Install Path%>/90/DTS/Bin/MsDtsSrvr.ini.xml file to set the <ServerName> property to the Virtual Server name. Correct? Why can't M$ do this for me?
2. Do I HAVE to export the SSIS package to a .DTSX file in order to be able to edit it with Visual Studio? Is there ANY way around this?
3. If I am running in a clustered environment and I use the File System for storing packages, then the pacakges must be stored on a shared volume, right?
4. I did not find SQL Server Integration services on the B- (Passive) node. Do I have to install it separately onto the B server (much like having to install the Client Tools)?
If anyone has some guidance or tips on running SSIS in this brave, new, wonderful world, I would sure appreciate it.
And yes, I am going to go out right now and order a new book on SSIS.
Regards,
hmscott
Hello,
When I try to save modifies in packages with many components the system show me a information dialog telling me that there was a System.OutOfMemoryException
Anyone knows how to solve this problem without divide the package in 2 or more packages?
HI Gurus,
What permissions one sholud have to cretae and execute SSIS packages.
Thanks,
ServerTeam
Hi All,
I've been assigned a task by one of the programmer in my team to create packages from some of the databases(One from SQL2005&Other one from SQLEXPRESS)
I've created and saved the packages using the export wizard.I saved the Packages as Integration Services Packages(On file System).
Now he wants me to execute the packages using SSIS But in different time,like maybe after 5min.Other package runs.
I really have no clue how to do that,I've added Both packages in SSIS,But i really dont know how to run them in different time.
If anyone could help please do so!
Hi Gurus,
How can i know SSIS packages history as this package is executed with issues or without issues
Thanks,
ServerTeam
Hi Gurus,
How can i know SSIS packages history as this package is executed with issues or without issues
Thanks,
ServerTeam
I am in a situation where we are redesigning our Datawarehouse. Currently we have our Datawarehouse in SQL 2000 and we are rebuilding from scratch in SQL 2005. This means that even though we will get the same tables but we are planning to rename each & every attribute to make it more meaningful.
The question is like this:
We can migrate the current DTS packages to SSIS but since all the ODBC connections , field names(attributes) will change is it worth it to leverages the DTS packages ?
Also we convert the julian date to gregorian date in our DTS packages but since SSIS has a feature to convert julian date it would be redundant to migrate the packages and my feeling is to create new packages in SSIS and start on a clean slate.
Is there anybody who was in such situation ?
Please advise.
Adarsh Mathur
I thought so but I'm looking for a couple of packages and I am not be able to find any there at all.