Wizard For Creating Interface To Ssis Package?
May 21, 2007
I'm very new to ssis, so I hope I don't sound too ignorant. I was told there might be a way to create User interfaces for ssis projects. ie, I am trying to create an import package that will let a user import an excel file to a sql table. What I would like to have is some sort of web interface that lets the user select the source file and destination table.
The more I search for a way to do this the more it seems impossible without knowing a ton about coding. If anyoen can help I'd appreciate it.
View 4 Replies
ADVERTISEMENT
Apr 18, 2006
HI,
I created a script component that is doing some transformations and it works very well. Now, I want to use the same script component on other dataflows in order to use it with other tables. Since my script component uses three outputs and some of my dimensions may have sometimes 50-60 columns, and the fact that I need to customize the column names used in my script, I would like to be able to have some kind of wizard like the SCD wizard to create columns into the outputs based on a list of columns that the user would and and input some columns (historical attributes, etc) into my script component logic .
Has anybody did that before, or is there some articles/samples where I could look in order to get me started in doing this?
Thank you,
Ccote
View 7 Replies
View Related
Dec 17, 2007
Hello All,
I am a newbe at MS SQL 2005, so if this has already been answered elsewhere, please just point me in the right direction.
I have successfully used the Import/Export wizard in "execute immediate" mode to import a table from Oracle 10g to MS SQL 2005. Works like a charm, but when I take the saved pacakge (saved as a *.dtsx server side file) - with no changes to the package and execute it from the either the "dos" prompt or from Windows explorer it fails at the login to Oracle step. Yet when I check the package's "Connection Managers" source connection, all the settings, user-ids and passwords look fine. The package does indeed execute, but I receive an ORA-01017:invalid username/password within the trace file of the package, but nothing has been changed from the Import/Export wizard which ran beatifully, thus verifying the appropriate acccess rights to Oracle.
Any advice would be greatly appreciated.
Doug
View 7 Replies
View Related
May 2, 2008
Hi All,
I am in the process of moving from a 32-bit SQL Server 2005 Enterprise (9.0.3054) to a 64-bit SQL Server 2005 Enterprise (9.0.3054 with 4 CPUs and 8GB of memory on Win 2003 SP2) and the process has been very frustrating to say the least. I am having a problem with packages that I created on my 64-bit SQL Server. I am importing a few tables from the 32-SQL Server into the 64-bit SQL Server using the Task --> Import to create the package.
Sometimes when I am creating a package I get the following error in a message box:
SQL Server Import and Export Wizard
The SSIS Runtime object could not be created. Verify that DTS.dll is available and registered. The wizard cannot continue and it will terminate.
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Windows.Forms)
Other times when I run a package that has run successfully before I get the following error:
Faulting application dtexecui.exe, version 9.0.3042.0, stamp 45cd726d, faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault address 0x025d23f0.
Other times I get this error message:
.NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (79FFEE24) (80131506)
And still other times
The package appears to hang when running. By this I mean that the Package Execution Progress shows progress up to a point then it just stops. (The package takes about 17 seconds to run normally) CPU usage is at 1% and the package cannot be stopped.
I have deleted and re-created the package several times and I have also re-installed the service pack on the SQL Server (9.0.3054) but that did not help.
Does anyone have any other suggestions to try?
Thanks.
View 4 Replies
View Related
Aug 3, 2006
I am trying to
copy a database from our company's external SQL
Server(production) to our local SQL
Server(development). The Copy Database wizard fails on the step
"Execute SQL Server Agent Job".
Following is the error in the log file.. Please advise
InnerException-->An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
View 7 Replies
View Related
Mar 5, 2007
HI All,
can any body give steps to import data from one sqldb to another through ssis package, i was comfotable with dts but ssis is a lil bit confusing.....
thnx
regards
View 1 Replies
View Related
Feb 18, 2008
Can anyone give a newbie a general script for creating an SSIS page to import data nightly from an Access database to sql 2005. They are not on the same server. The Access database us 366,968 kb and grows everyday from input from web content. It has 5 tables and 100's of queries, which is how it is updated.
Please give me a starting point, do not understand the info in books on line.
Thank you
Dee
View 6 Replies
View Related
Mar 12, 2006
Following is what I would like to do, so I can keep updating my central SQL Server database with latest updates from the field. I like to use SSIS 2005 to create a package that could do this. Any help to get me started would be appreciated. I need some help soon, pls give me something to get started. APpreciate it. Thanks.
Open connection and read client location table on the local SQL Server database called PODO
For each location id in the table do the following:
Store locationid/clientid in a variable called CLLOC_ID
Construct file name with mdb extension and store in a variable MDB_FILE
Establish connection to the data import folder
Search for that MDB_FILE in the folder on the file system
If there is a file where match = true then do this:
1) Open the access database
2) Read and import the data from the customer experience table
3) Write that data to the SQL Server tables where location = CLLOC_ID
4) Exit process
IF there is no match, exit process
Keep looping until all the client ids/loc ids are read from the SQL Server client location table.
MA
View 4 Replies
View Related
Jan 4, 2007
Hi guys,
I was intended to write a program that will create a SSIS package which will import data from a CSV file to the SQL server 2005. But I did not find any good example for this into the internet. I found some example which exports data from SQL server 2005 to CSV files. And following those examples I have tried to write my own. But I am facing some problem with that. What I am doing here is creating two connection manager objects, one for Flat file and another for OLEDB. And create a data flow task that has two data flow component, one for reading source and another for writing to destination. While debugging I can see that after invoking the ReinitializedMetaData() for the flat file source data flow component, there is not output column found. Why it is not fetching the output columns from the CSV file? And after that when it invokes the ReinitializedMetaData() for the destination data flow component it simply throws exception.
Can any body help me to get around this problem? Even can anyone give me any link where I can find some useful article to accomplish this goal?
I am giving my code here too.
I will appreciate any kind of suggestion on this.
Code snippet:
public void CreatePackage()
{
string executeSqlTask = typeof(ExecuteSQLTask).AssemblyQualifiedName;
Package pkg = new Package();
pkg.PackageType = DTSPackageType.DTSDesigner90;
ConnectionManager oledbConnectionManager = CreateOLEDBConnection(pkg);
ConnectionManager flatfileConnectionManager =
CreateFileConnection(pkg);
// creating the SQL Task for table creation
Executable sqlTaskExecutable = pkg.Executables.Add(executeSqlTask);
ExecuteSQLTask execSqlTask = (sqlTaskExecutable as Microsoft.SqlServer.Dts.Runtime.TaskHost).InnerObject as ExecuteSQLTask;
execSqlTask.Connection = oledbConnectionManager.Name;
execSqlTask.SqlStatementSource =
"CREATE TABLE [MYDATABASE].[dbo].[MYTABLE] ([NAME] NVARCHAR(50),[AGE] NVARCHAR(50),[GENDER] NVARCHAR(50)) GO";
// creating the Data flow task
Executable dataFlowExecutable = pkg.Executables.Add("DTS.Pipeline.1");
TaskHost pipeLineTaskHost = (TaskHost)dataFlowExecutable;
MainPipe dataFlowTask = (MainPipe)pipeLineTaskHost.InnerObject;
// Put a precedence constraint between the tasks.
PrecedenceConstraint pcTasks = pkg.PrecedenceConstraints.Add(sqlTaskExecutable, dataFlowExecutable);
pcTasks.Value = DTSExecResult.Success;
pcTasks.EvalOp = DTSPrecedenceEvalOp.Constraint;
// Now adding the data flow components
IDTSComponentMetaData90 sourceDataFlowComponent = dataFlowTask.ComponentMetaDataCollection.New();
sourceDataFlowComponent.Name = "Source Data from Flat file";
// Here is the component class id for flat file source data
sourceDataFlowComponent.ComponentClassID = "{90C7770B-DE7C-435E-880E-E718C92C0573}";
CManagedComponentWrapper managedInstance = sourceDataFlowComponent.Instantiate();
managedInstance.ProvideComponentProperties();
sourceDataFlowComponent.
RuntimeConnectionCollection[0].ConnectionManagerID = flatfileConnectionManager.ID;
sourceDataFlowComponent.
RuntimeConnectionCollection[0].ConnectionManager = DtsConvert.ToConnectionManager90(flatfileConnectionManager);
managedInstance.AcquireConnections(null);
managedInstance.ReinitializeMetaData();
managedInstance.ReleaseConnections();
// Get the destination's default input and virtual input.
IDTSOutput90 output = sourceDataFlowComponent.OutputCollection[0];
// Here I dont find any columns at all..why??
// Now adding the data flow components
IDTSComponentMetaData90 destinationDataFlowComponent = dataFlowTask.ComponentMetaDataCollection.New();
destinationDataFlowComponent.Name =
"Destination Oledb compoenent";
// Here is the component class id for Oledvb data
destinationDataFlowComponent.ComponentClassID = "{E2568105-9550-4F71-A638-B7FE42E66922}";
CManagedComponentWrapper managedOleInstance = destinationDataFlowComponent.Instantiate();
managedOleInstance.ProvideComponentProperties();
destinationDataFlowComponent.
RuntimeConnectionCollection[0].ConnectionManagerID = oledbConnectionManager.ID;
destinationDataFlowComponent.
RuntimeConnectionCollection[0].ConnectionManager = DtsConvert.ToConnectionManager90(oledbConnectionManager);
// Set the custom properties.
managedOleInstance.SetComponentProperty("AccessMode", 2);
managedOleInstance.SetComponentProperty("OpenRowset", "[MYDATABASE].[dbo].[MYTABLE]");
managedOleInstance.AcquireConnections(null);
managedOleInstance.ReinitializeMetaData(); // Throws exception
managedOleInstance.ReleaseConnections();
// Create the path.
IDTSPath90 path = dataFlowTask.PathCollection.New(); path.AttachPathAndPropagateNotifications(sourceDataFlowComponent.OutputCollection[0],
destinationDataFlowComponent.InputCollection[0]);
// Get the destination's default input and virtual input.
IDTSInput90 input = destinationDataFlowComponent.InputCollection[0];
IDTSVirtualInput90 vInput = input.GetVirtualInput();
// Iterate through the virtual input column collection.
foreach (IDTSVirtualInputColumn90 vColumn in vInput.VirtualInputColumnCollection)
{
managedOleInstance.SetUsageType(
input.ID, vInput, vColumn.LineageID, DTSUsageType.UT_READONLY);
}
DTSExecResult res = pkg.Execute();
}
public ConnectionManager CreateOLEDBConnection(Package p)
{
ConnectionManager ConMgr;
ConMgr = p.Connections.Add("OLEDB");
ConMgr.ConnectionString =
"Data Source=VSTS;Initial Catalog=MYDATABASE;Provider=SQLNCLI;Integrated Security=SSPI;Auto Translate=false;";
ConMgr.Name = "SSIS Connection Manager for Oledb";
ConMgr.Description = "OLE DB connection to the Test database.";
return ConMgr;
}
public ConnectionManager CreateFileConnection(Package p)
{
ConnectionManager connMgr;
connMgr = p.Connections.Add("FLATFILE");
connMgr.ConnectionString = @"D:MyCSVFile.csv";
connMgr.Name = "SSIS Connection Manager for Files";
connMgr.Description = "Flat File connection";
connMgr.Properties["Format"].SetValue(connMgr, "Delimited");
connMgr.Properties["HeaderRowDelimiter"].SetValue(connMgr, Environment.NewLine);
return connMgr;
}
And my CSV files is as follows
NAME, AGE, GENDER
Jon,52,MALE
Linda, 26, FEMALE
Thats all. Thanks.
View 4 Replies
View Related
Aug 6, 2007
Hi,
I'm trying to create a SSIS package. I have used OLEDBSource adapter to get the source table's data and transferring the data to an OLEDBDestination adapter. I tried but I'm facing the problem in mapping the metadata contents.
My code:
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
static void Main(string[] args)
{
// Create a new package
Package package = new Package();
package.Name = "OLE DB Transfer";
// Add a Data Flow task
TaskHost taskHost = package.Executables.Add("DTS.Pipeline") as TaskHost;
taskHost.Name = "Transfer Table";
IDTSPipeline90 pipeline = taskHost.InnerObject as MainPipe;
// Get the pipeline's component metadata collection
IDTSComponentMetaDataCollection90 componentMetadataCollection = pipeline.ComponentMetaDataCollection;
// Add a new component metadata object to the data flow
IDTSComponentMetaData90 oledbSourceMetadata = componentMetadataCollection.New();
// Associate the component metadata object with the OLE DB Source Adapter
oledbSourceMetadata.ComponentClassID = "DTSAdapter.OLEDBSource";
// Instantiate the OLE DB Source adapter
IDTSDesigntimeComponent90 oledbSourceComponent = oledbSourceMetadata.Instantiate();
// Ask the component to set up its component metadata object
oledbSourceComponent.ProvideComponentProperties();
// Add an OLE DB connection manager
ConnectionManager connectionManagerSource = package.Connections.Add("OLEDB");
connectionManagerSource.Name = "OLEDBSource";
// Set the connection string
connectionManagerSource.ConnectionString = "provider=sqlncli;server=HSCHBSCGN25008;integrated security=sspi;database=Muthu_SSIS_Testing";
// Set the connection manager as the OLE DB Source adapter's runtime connection
IDTSRuntimeConnection90 runtimeConnectionSource = oledbSourceMetadata.RuntimeConnectionCollection["OleDbConnection"];
runtimeConnectionSource.ConnectionManagerID = connectionManagerSource.ID;
// Tell the OLE DB Source adapter to use the SQL Command access mode.
oledbSourceComponent.SetComponentProperty("AccessMode", 2);
// Set up the SQL command
oledbSourceComponent.SetComponentProperty("SqlCommand", "select * from EmployeeTable");
// Set up the connection manager object
runtimeConnectionSource.ConnectionManager = DtsConvert.ToConnectionManager90(connectionManagerSource);
// Establish the database connection
oledbSourceComponent.AcquireConnections(null);
// Set up the column metadata
oledbSourceComponent.ReinitializeMetaData();
// Release the database connection
oledbSourceComponent.ReleaseConnections();
// Release the connection manager
runtimeConnectionSource.ReleaseConnectionManager();
// Add a new component metadata object to the data flow
IDTSComponentMetaData90 oledbDestinationMetadata = componentMetadataCollection.New();
//Associate the component metadata object with the OLE DB Destination Adapter
oledbDestinationMetadata.ComponentClassID = "DTSAdapter.OLEDBDestination";
// Instantiate the OLE DB Destination adapter
IDTSDesigntimeComponent90 oledbDestinationComponent = oledbDestinationMetadata.Instantiate();
// Ask the component to set up its component metadata object
oledbDestinationComponent.ProvideComponentProperties();
// Add an OLE DB connection manager
ConnectionManager connectionManagerDestination = package.Connections.Add("OLEDB");
connectionManagerDestination.Name = "OLEDBDestination";
// Set the connection string
connectionManagerDestination.ConnectionString = "provider=sqlncli;server=HSCHBSCGN25008;integrated security=sspi;database=Muthu_SSIS_Testing";
// Set the connection manager as the OLE DB Destination adapter's runtime connection
IDTSRuntimeConnection90 runtimeConnectionDestination = oledbDestinationMetadata.RuntimeConnectionCollection["OleDbConnection"];
runtimeConnectionDestination.ConnectionManagerID = connectionManagerDestination.ID;
// Tell the OLE DB Destination adapter to use the SQL Command access mode.
oledbDestinationComponent.SetComponentProperty("AccessMode", 2);
// Set up the SQL command
oledbDestinationComponent.SetComponentProperty("SqlCommand", "select from EmplTable");
// Set up the connection manager object
runtimeConnectionDestination.ConnectionManager = DtsConvert.ToConnectionManager90(connectionManagerDestination);
// Get the standard output of the OLE DB Source adapter
IDTSOutput90 oledbSourceOutput = oledbSourceMetadata.OutputCollection["OLE DB Source Output"];
// Get the input of the OLE DB Destination adapter
IDTSInput90 oledbDestinationInput = oledbDestinationMetadata.InputCollection["OLE DB Destination Input"];
// Create a new path object
IDTSPath90 path = pipeline.PathCollection.New();
// Connect the source and destination adapters
path.AttachPathAndPropagateNotifications(oledbSourceOutput, oledbDestinationInput);
IDTSInput90 input = oledbDestinationInput;
IDTSVirtualInput90 vInput = input.GetVirtualInput();
foreach (IDTSVirtualInputColumn90 vColumn in vInput.VirtualInputColumnCollection)
{
// Call the SetUsageType method of the destination
// to add each available virtual input column as an input column.
oledbDestinationComponent.SetUsageType(
input.ID, vInput, vColumn.LineageID, DTSUsageType.UT_READONLY);
}
foreach (IDTSInputColumn90 col in oledbDestinationInput.InputColumnCollection)
{
IDTSExternalMetadataColumn90 exCol = oledbDestinationInput.ExternalMetadataColumnCollection[col.Name];
oledbDestinationComponent.MapInputColumn(oledbDestinationInput.ID, col.ID, exCol.ID);
}
Console.WriteLine("done");
Console.ReadKey();
// Save the package
//Application application = new Application();
//application.SaveToXml(@"c:OLEDBTransfer.dtsx", package, null);
}
While debugging, I'm getting exception (ELEMENTNOTFOUND) at this line
IDTSExternalMetadataColumn90 exCol = oledbDestinationInput.ExternalMetadataColumnCollection[col.Name];
because metadata have no appropriate column to map with the destination component.
Any one help me to resolve this issue.
Regards,
kris
View 1 Replies
View Related
Jan 7, 2014
I have a ssis package in the DW environment. How can I run this package in the production environment by creating the job and run remotely.
View 7 Replies
View Related
Sep 11, 2007
I would like to create an event handler that would catch any errors that result from a sys.<table> not existing. The package is designed to run on both SQL Server 2000 and SQL Server 2005 and when I query sys.<tables> there is an error when the query is run on SQL Server 2000. I just need a good starting point...I would like something that when the server isn't 2005 it just skips the server and doesn't fail the package and doesn't get counted towards the max error count. Thanks for any help.
-Kyle
View 1 Replies
View Related
Sep 29, 2006
I need to run a make-table query against an Access database out of an SSIS package. I tried to do this with an OLE DB Command Task but it fails to create the table even though the task execution comes back successful. Any thoughts???
View 1 Replies
View Related
Sep 26, 2007
Hi,
I want to create a local temporary table in execute sql task and and want to use the same in Data flow task as source table.
I follow the following steps to achieve this:
01. Created a new SSIS package
02. Create a connection string to "(local)/." server, "tempdb" database
03. Set the "RetainSameConnection" property value to "TRUE"
04. Set the "DelayValidation" to "TRUE", where ever I found this property
04. In Control Flow I added to items
a. Execute SQL Task
b. Data Flow Task
05. For "Execute SQL task" I set the connection to "tempdb"
06. I written the following query
Create table #transfer_CompaniesToProcess_tbl
(
companyID int not null
)
GO
07. In Data Flow task I added "OLE DB Source" and "OLE DB Destination"
08. In "OLE DB Source" I changed the "Data access mode:" to "SQL command"
09. In "SQL command text:" I entered "select * from #transfer_CompaniesToProcess_tbl"
10. When I clicked on the "OK" button; I ended with following error:
TITLE: Microsoft Visual Studio
------------------------------
Error at Data Flow Task [OLE DB Source [1]]: An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Statement(s) could not be prepared.".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Invalid object name '#transfer_CompaniesToProcess_tbl'.".
------------------------------
ADDITIONAL INFORMATION:
Exception from HRESULT: 0xC0202009 (Microsoft.SqlServer.DTSPipelineWrap)
------------------------------
BUTTONS:
OK
------------------------------
I gone through the following article and it seems I missed some thing.
http://blogs.conchango.com/jamiethomson/archive/2006/11/19/SSIS_3A00_-Using-temporary-tables.aspx
Can any one have any idea where I am doing wrong?
Thanks
Sreekanth
View 9 Replies
View Related
Apr 18, 2007
Trying to figure out the best method of reading in a number of flat files, all with different number of columns and data types and outputting them to a database.
Here's the problem: They are EBCDIC encoded and some of the columns are packed decimal. I've set up one package that takes the flat file, unpacks the decimal (Using UnpackDecimal component) and then sending the rest through a second component to go from EBCDIC -> ASCII.
What I need is a way to do this for every flat file based on the schema for that flat file. One current solution is to write a script/app to create the .dtsx XML file and then execute that for each flat file. It appears like this may be possible, but I haven't gotten far enough to know for sure. So my questions are this:
1) Is there an easier way to do this (ie somehow feed the schema to the package and use it to dynamically set up the column makers and determine which columns get fed to the unpack decimal component.
2) If there isn't a better way, will dynamically creating the .dtsx XML file based on the necessary input/output columns for each flat file work? If so, what is a good source of information on this (information about how the .dtsx XML file is set up, what needs to be changed/what doesn't, etc).
Thanks,
Travis
View 1 Replies
View Related
Jun 13, 2006
In the tutorial Creating a Basic Package Using a Wizard > Lesson 1: Creating the Basic Package >
says to use the following sql statement on the query page:
SELECT * FROM [Customers$] WHERE NumberCarsOwned > 0
When I paste the query in I get the message :
This SQL statement is not a query.
Does anyone have any suggestions? The input and output are set up correctly and I have the sample excel file Customers.xls.
I am new to all this, is there some setting I need to change for the tutorial to work or..?
FYI I have installed Sql 2005, Sp1.
View 4 Replies
View Related
Apr 8, 2008
Hi All,
I have created fact tables and dimension tables in datawarehouse database, and i created a olap cube from those tables.
I want to run SSIS Package which populates these fact and dimension tables from datasources.
Thanks in advance,
Archana
View 5 Replies
View Related
Mar 12, 2008
Hi
I have a problem i receive the following error message when i try to add an new step into a SQL Server Agent job :
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
Additional information:
An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.(Microsoft SQL Server, Error: 3930)
This error pops up right after i change the type of the step to "SQL Server Intergration Services Package"
I have made the following configurations:
The user group (windows group) that the user belongs has the following roles in msdb :
db_dtsadmin
db_dtsltuser
db_dtsoperator
SQLAgentOperatorRole
SQLAgentReaderRole
SQLAgentUserRole
i have made a proxy to sql server agent which has the following subsystems :
"SQL Server Integration Services Provider" the proxy is tied to the same login which has those SQLagent and dts roles in msdb database.
Im using windows authentication and the user that logs into the sql server is in the same group that i have set all of the rights.
Ps. Clearly im missing some role or right somewhere because as soon as i give the group sysadmin role then all the users in that group can create SSIS steps in the agent.
Ps. Ps. I have been living under the impression that i dont have to give sysadmin rights to people that create ssis packages and schedule then with the agent.
View 1 Replies
View Related
Apr 26, 2007
Hi guys,
I'm a newbie DBA and i'm trying to create a package that would extract data from MySQL and inserts them to a SQL 2005 Server. I'm quite new to this SSIS and would like to ask help from you to help me go through with this.
I hope you guys can help me with this.
Hoping to hear from you soon.
Thank you so much.
Kind regards,
Neil
View 7 Replies
View Related
Jan 26, 2006
I am running a package from a C# application. I would like to use the IDTSEvents interface to capture events from the package such as OnPreExecute, OnWarning, OnError, etc. I created a class (PackageEvents) that implements the IDTSEvents interface. I pass a PackageEvents object into the Application.LoadPackage call that creates the package. The package runs successfully as usual, but nothing happens in my PackageEvents class. None of the breakpoints hit (I put one in every function).
What do I need to do to get the class that implements IDTSEvents to be called? All the properties of the package object seem reasonable at runtime.
Here is a code snippet that shows what I am trying to do:
// Class that implements the IDTSEvents interface:
public sealed class PackageEvents : IDTSEvents
{
void IDTSEvents.OnPreExecute(Executable exec, ref bool fireAgain)
{
Console.WriteLine("OnPreExecute");
}
....
// Code to run the package
Application app = new Application();
// PackageEvents implements IDTSEvent (see above)
PackageEvents packageEvents = new PackageEvents();
Package package = app.LoadPackage("C:\temp\Package.dtsx", packageEvents);
DTSExecResult result = package.Execute();
View 8 Replies
View Related
Feb 21, 2006
Hi there,
we have several DWH Load processes running in SSIS, however I want to enable the enduser to have more control and information about the status of these processes. Therefore I plan to write a monitoring interface based on ASP.NET 2.0. However I hardly could find good docu or samples on what is available from within ASP.NET 2.0 to read out or control SSIS.
Anybody having me some good pointers to start with ?
View 2 Replies
View Related
Mar 20, 2007
can i create a table within the aspnetdb.mdf???
I created a database from SQL server set up wizard, and the
database i make copy exactly what a aspnetdb.mdf(from tables to
stored procedure) has..Can i change or add some files,tbles and
stored procedure to it...
I'll using SQL Express Edition...
can i know what is the best way to implement the database i created
if im going to setup ,manually my database (without set up
wizard)can I copy the tables and stored procedure in aspnetdb.mdf
in my database??
thanks for the answer...
thanks and more power...
View 1 Replies
View Related
May 19, 2004
When I run the database copy wizard I'm getting an error creating shared omwwize.
The source server is 7.0. The destination server is 2000. I'm invoking the wizard from the 2000 machine.
Anybody know what this error means?
Thanks
Sharon
View 1 Replies
View Related
Jul 11, 2007
Run the SSIS import/export wizard.
(xls -> sql table)
Select the tasks created.
Copy.
Here is the error that occurs.
p.s. Does anyone have any needles I can borrow? I think sticking them in my eyes would be nicer than working with SSIS.
===================================
An error occurred while objects were being copied. SSIS Designer could not serialize the SSIS runtime objects. (Microsoft Visual Studio)
===================================
Could not copy object 'Preparation SQL Task' to the clipboard.
(Microsoft.DataTransformationServices.Design)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.762&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=SerializeComponentsFailed&LinkId=20476
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Design.DtsClipboardCommandHelper.SerializeRuntimeObjects(ICollection logicalObjects)
at Microsoft.DataTransformationServices.Design.ControlFlowClipboardCommandHelper.InternalMenuCopy(MenuCommand sender, CommandHandlingArgs args)
===================================
Invalid access to memory location. (Exception from HRESULT: 0x800703E6) (Microsoft.SqlServer.ManagedDTS)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.PersistImpl.SaveToXML(XmlDocument& doc, XmlNode node, IDTSEvents events)
at Microsoft.SqlServer.Dts.Runtime.DtsContainer.SaveToXML(XmlDocument& doc, XmlNode node, IDTSEvents events)
at Microsoft.DataTransformationServices.Design.DtsClipboardCommandHelper.SerializeRuntimeObjects(ICollection logicalObjects)
View 14 Replies
View Related
Aug 30, 2006
Hey, I've a few jobs which call SSIS packages. If I run the SSIS package, it runs fine but if I try to run the job which calls this package, it fails. Can someone help me troubleshoot this issue? None of my jobs that call an SSIS package work. All of them fail.
Thank you
Tej
View 7 Replies
View Related
Nov 4, 2006
Hi,
I am new to SSIS. I followed the direction of the tutorial Creating Simple ETL Tutorial package in BooksOnline. I have tried more than five times and have done exactly as suggested in the tutorial but it does not work.
The URL is:
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
I get these warnings and finally fails:
1)[Lookup [30]] Error: Row yielded no match during lookup.
2) [Lookup [30]] Error: The "component "Lookup" (30)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Output" (32)" specifies failure on error. An error occurred on the specified object of the specified component.
3) [DTS.Pipeline] Error: The ProcessInput method on component "Lookup" (30) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
4) [DTS.Pipeline] Error: Thread "WorkThread0" has exited with error code 0xC0209029.
Can someone help me with this tutorial error? or Am I doing something wrong.
Thank you,
View 6 Replies
View Related
Apr 11, 2008
Hi. I've created a number of packages in SSIS which just make temp tables out of views. I did them with the "Optimize for many tables" and "Run in transaction" boxes checked.
Now I'm trying to port them over to another database on another server. I'm first going through the Package Configuration Wizard. When I try to finish the wizard I get a error with the following message:
quote:===================================
Could not complete wizard actions. (Microsoft Visual Studio)
===================================
Could not generate the configuration file. (Microsoft.DataTransformationServices.Wizards)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Wizards.ConfigurationWizardPages.ConfigurationWizardSR&EvtID=CouldNotGenerateConfigurationFile&LinkId=20476
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Wizards.ConfigurationWizardForm.GenerateXmlConfigurationFile(DesignTimeConfiguration designTimeConfiguration)
at Microsoft.DataTransformationServices.Wizards.ConfigurationWizardForm.OnFinish(CancelEventArgs e)
===================================
Failure exporting configuration file.
(ENRLMNT_UniqueRecords_temp)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Package.ExportConfigurationFile(String str)
at Microsoft.DataTransformationServices.Wizards.ConfigurationWizardForm.GenerateXmlConfigurationFile(DesignTimeConfiguration designTimeConfiguration)
I don't know how to resolve it. Anyone?
One way to deal with this particular issue would be just to recreate the SSIS package on the other server. The issue with this is I want to be positive which view I'm making a copy of and I'm not currently. Since the Import/Export has the transaction setting checked, I can't seem to determine what the source was. Help?
View 2 Replies
View Related
Mar 13, 2007
In Visual Studion I invoke the wizard, indicate the source for the DTS packages and pick a folder for the migrated package but I don't get a list of my source packages. Instead, I get the error message, 'index out of range, must be non negative, parameter name index(mscorlib)'.
Has anyone ever gotten this error. What does it mean and how can I fix it?
Thanks in advance,
View 1 Replies
View Related
Aug 9, 2006
I am attempting to create an XML Configuration file and I am recieving the following error once I click finish in the wizard:
Could not complete wizard actions.
Additional Information:
Could not generate the configuration file. (Microsoft.Data.TransformationServices.Wizard)
Technical Details:
===================================
Could not complete wizard actions. (Microsoft Visual Studio)
===================================
Could not generate the configuration file. (Microsoft.DataTransformationServices.Wizards)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Wizards.ConfigurationWizardPages.ConfigurationWizardSR&EvtID=CouldNotGenerateConfigurationFile&LinkId=20476
------------------------------
Program Location:
at Microsoft.DataTransformationServices.Wizards.ConfigurationWizardForm.GenerateXmlConfigurationFile(DesignTimeConfiguration designTimeConfiguration)
at Microsoft.DataTransformationServices.Wizards.ConfigurationWizardForm.OnFinish(CancelEventArgs e)
===================================
Failure exporting configuration file.
(eFreedomAS)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Package.ExportConfigurationFile(String str)
at Microsoft.DataTransformationServices.Wizards.ConfigurationWizardForm.GenerateXmlConfigurationFile(DesignTimeConfiguration designTimeConfiguration)
Name:
eFreedomAS2
Type:
Configuration File
New configuration file will be created.
File name:
C:abc.xml
Properties:
Package.Variables[User::SourcePath].Properties[Value]
Package.Variables[User::SourcePath].Properties[Name]
Package.Variables[User::Packages].Properties[Value]
Package.Variables[User::Packages].Properties[Name]
Package.Variables[User::PackageDefNumber].Properties[Value]
Package.Variables[User::PackageDefNumber].Properties[Name]
Package.Variables[User::Directory].Properties[Value]
Package.Variables[User::Directory].Properties[Name]
Package.Variables[User::DestinationPath].Properties[Value]
Package.Variables[User::DestinationPath].Properties[Name]
Package.Connections[ViewHelpTopicDef].Properties[Name]
Package.Connections[ViewHelpTopicDef].Properties[ConnectionString]
Package.Connections[ViewDef].Properties[Name]
Package.Connections[ViewDef].Properties[ConnectionString]
Package.Connections[ValidationTestDef].Properties[Name]
Package.Connections[ValidationTestDef].Properties[ConnectionString]
Package.Connections[ValidationRulePackageDef].Properties[Name]
Package.Connections[ValidationRulePackageDef].Properties[ConnectionString]
Package.Connections[ValidationRuleFileDef].Properties[Name]
Package.Connections[ValidationRuleFileDef].Properties[ConnectionString]
Package.Connections[ValidationRuleDef].Properties[Name]
Package.Connections[ValidationRuleDef].Properties[ConnectionString]
Package.Connections[ValidationMessageFileDef].Properties[Name]
Package.Connections[ValidationMessageFileDef].Properties[ConnectionString]
Package.Connections[ValidationMessageDef].Properties[Name]
Package.Connections[ValidationMessageDef].Properties[ConnectionString]
Package.Connections[ValidationIdentifierDependency].Properties[Name]
Package.Connections[ValidationIdentifierDependency].Properties[ConnectionString]
Package.Connections[ValidationCalcGraphEdge].Properties[Name]
Package.Connections[ValidationCalcGraphEdge].Properties[ConnectionString]
Package.Connections[UserGroupFeatureDef].Properties[Name]
Package.Connections[UserGroupFeatureDef].Properties[ConnectionString]
Package.Connections[UserGroupFeature].Properties[Name]
Package.Connections[UserGroupFeature].Properties[ConnectionString]
Package.Connections[UserGroupDef].Properties[Name]
Package.Connections[UserGroupDef].Properties[ConnectionString]
Package.Connections[UserGroup].Properties[Name]
Package.Connections[UserGroup].Properties[ConnectionString]
Package.Connections[TableDef].Properties[Name]
Package.Connections[TableDef].Properties[ConnectionString]
Package.Connections[Source].Properties[UserName]
Package.Connections[Source].Properties[ServerName]
Package.Connections[Source].Properties[Password]
Package.Connections[Source].Properties[Name]
Package.Connections[Source].Properties[InitialCatalog]
Package.Connections[Source].Properties[ConnectionString]
Package.Connections[SelectListItemDef].Properties[Name]
Package.Connections[SelectListItemDef].Properties[ConnectionString]
Package.Connections[SelectListDef].Properties[Name]
Package.Connections[SelectListDef].Properties[ConnectionString]
Package.Connections[ScriptAssemblyDef].Properties[Name]
Package.Connections[ScriptAssemblyDef].Properties[ConnectionString]
Package.Connections[PrintedPageFormulaScriptDef].Properties[Name]
Package.Connections[PrintedPageFormulaScriptDef].Properties[ConnectionString]
Package.Connections[PageDef].Properties[Name]
Package.Connections[PageDef].Properties[ConnectionString]
Package.Connections[PageCalcPathSubPath].Properties[Name]
Package.Connections[PageCalcPathSubPath].Properties[ConnectionString]
Package.Connections[PageCalcPath].Properties[Name]
Package.Connections[PageCalcPath].Properties[ConnectionString]
Package.Connections[PackageLinkDef].Properties[Name]
Package.Connections[PackageLinkDef].Properties[ConnectionString]
Package.Connections[PackageImportTypeDef].Properties[Name]
Package.Connections[PackageImportTypeDef].Properties[ConnectionString]
Package.Connections[PackageIdentifierGroupDef].Properties[Name]
Package.Connections[PackageIdentifierGroupDef].Properties[ConnectionString]
Package.Connections[PackageIdentifierDef].Properties[Name]
Package.Connections[PackageIdentifierDef].Properties[ConnectionString]
Package.Connections[PackageExportTypeDef].Properties[Name]
Package.Connections[PackageExportTypeDef].Properties[ConnectionString]
Package.Connections[PackageDef].Properties[Name]
Package.Connections[PackageDef].Properties[ConnectionString]
Package.Connections[PackageDataItemTextDef].Properties[Name]
Package.Connections[PackageDataItemTextDef].Properties[ConnectionString]
Package.Connections[OnlinePagePrintedPageDef].Properties[Name]
Package.Connections[OnlinePagePrintedPageDef].Properties[ConnectionString]
Package.Connections[OnlinePageDefDependency].Properties[Name]
Package.Connections[OnlinePageDefDependency].Properties[ConnectionString]
Package.Connections[OnlinePageDef].Properties[Name]
Package.Connections[OnlinePageDef].Properties[ConnectionString]
Package.Connections[MaterialityToleranceDef].Properties[Name]
Package.Connections[MaterialityToleranceDef].Properties[ConnectionString]
Package.Connections[LineDef].Properties[Name]
Package.Connections[LineDef].Properties[ConnectionString]
Package.Connections[ImportTypeDef].Properties[Name]
Package.Connections[ImportTypeDef].Properties[ConnectionString]
Package.Connections[ImportDef].Properties[Name]
Package.Connections[ImportDef].Properties[ConnectionString]
Package.Connections[IdentifierStateDef].Properties[Name]
Package.Connections[IdentifierStateDef].Properties[ConnectionString]
Package.Connections[IdentifierRelatedDef].Properties[Name]
Package.Connections[IdentifierRelatedDef].Properties[ConnectionString]
Package.Connections[IdentifierPrintReferenceDef].Properties[Name]
Package.Connections[IdentifierPrintReferenceDef].Properties[ConnectionString]
Package.Connections[IdentifierGroupUserGroupFeatureDef].Properties[Name]
Package.Connections[IdentifierGroupUserGroupFeatureDef].Properties[ConnectionString]
Package.Connections[IdentifierGroupUserGroupFeature].Properties[Name]
Package.Connections[IdentifierGroupUserGroupFeature].Properties[ConnectionString]
Package.Connections[IdentifierGroupIdentifierDef].Properties[Name]
Package.Connections[IdentifierGroupIdentifierDef].Properties[ConnectionString]
Package.Connections[IdentifierGroupIdentifier].Properties[Name]
Package.Connections[IdentifierGroupIdentifier].Properties[ConnectionString]
Package.Connections[IdentifierGroupDef].Properties[Name]
Package.Connections[IdentifierGroupDef].Properties[ConnectionString]
Package.Connections[IdentifierGroup].Properties[Name]
Package.Connections[IdentifierGroup].Properties[ConnectionString]
Package.Connections[IdentifierDef].Properties[Name]
Package.Connections[IdentifierDef].Properties[ConnectionString]
Package.Connections[IdentifierDataItemTextDef].Properties[Name]
Package.Connections[IdentifierDataItemTextDef].Properties[ConnectionString]
Package.Connections[FormulaScriptDef].Properties[Name]
Package.Connections[FormulaScriptDef].Properties[ConnectionString]
Package.Connections[FormulaDef].Properties[Name]
Package.Connections[FormulaDef].Properties[ConnectionString]
Package.Connections[FeatureGroupFeatureDef].Properties[Name]
Package.Connections[FeatureGroupFeatureDef].Properties[ConnectionString]
Package.Connections[FeatureGroupDef].Properties[Name]
Package.Connections[FeatureGroupDef].Properties[ConnectionString]
Package.Connections[FeatureDef].Properties[Name]
Package.Connections[FeatureDef].Properties[ConnectionString]
Package.Connections[ExportTypeRelatedDef].Properties[Name]
Package.Connections[ExportTypeRelatedDef].Properties[ConnectionString]
Package.Connections[ExportTypeFormulaScriptDef].Properties[Name]
Package.Connections[ExportTypeFormulaScriptDef].Properties[ConnectionString]
Package.Connections[ExportTypeExportDef].Properties[Name]
Package.Connections[ExportTypeExportDef].Properties[ConnectionString]
Package.Connections[ExportTypeDef].Properties[Name]
Package.Connections[ExportTypeDef].Properties[ConnectionString]
Package.Connections[ExportTypeBlobTypeDef].Properties[Name]
Package.Connections[ExportTypeBlobTypeDef].Properties[ConnectionString]
Package.Connections[ExportFormulaScriptDef].Properties[Name]
Package.Connections[ExportFormulaScriptDef].Properties[ConnectionString]
Package.Connections[ExportDef].Properties[Name]
Package.Connections[ExportDef].Properties[ConnectionString]
Package.Connections[ColumnHeaderDef].Properties[Name]
Package.Connections[ColumnHeaderDef].Properties[ConnectionString]
Package.Connections[ColumnDef].Properties[Name]
Package.Connections[ColumnDef].Properties[ConnectionString]
Package.Connections[CellTypeFileTypeDef].Properties[Name]
Package.Connections[CellTypeFileTypeDef].Properties[ConnectionString]
Package.Connections[CellTypeDef].Properties[Name]
Package.Connections[CellTypeDef].Properties[ConnectionString]
Package.Connections[CellRangeDef].Properties[Name]
Package.Connections[CellRangeDef].Properties[ConnectionString]
Package.Connections[CellRangeCellDef].Properties[Name]
Package.Connections[CellRangeCellDef].Properties[ConnectionString]
Package.Connections[CellOverrideDef].Properties[Name]
Package.Connections[CellOverrideDef].Properties[ConnectionString]
Package.Connections[CellDef].Properties[Name]
Package.Connections[CellDef].Properties[ConnectionString]
Package.Connections[CategoryDef].Properties[Name]
Package.Connections[CategoryDef].Properties[ConnectionString]
Package.Connections[CalcPathSubPath].Properties[Name]
Package.Connections[CalcPathSubPath].Properties[ConnectionString]
Package.Connections[CalcPath].Properties[Name]
Package.Connections[CalcPath].Properties[ConnectionString]
Package.Connections[CalcGraphEdge].Properties[Name]
Package.Connections[CalcGraphEdge].Properties[ConnectionString]
Package.Connections[AreaDef].Properties[Name]
Package.Connections[AreaDef].Properties[ConnectionString]
View 4 Replies
View Related
Mar 12, 2008
I was working on a flat file import spec yesterday, using the import wizard, and I saved my work as a SSIS package. Today, if I connect to Integration Services through SQL Management Studio, I can see the package, but I can't edit it. I've tried to open the package using BIDS, but I can't find it on the server. Obviously it exists, but where?
How the heck can I edit this package? And, where is it? I don't understand why things are so much more difficult in 2005 vs. 2000.
Thanks.
View 4 Replies
View Related
Nov 10, 2005
I am unable to migrate any DTS packages, from a SQL Server 2000 package, from a structured storage file, or from a DTS package imported into SQL2005 (Developer Edition, 32 bit). Running the Package Migration Wizard, every time I get to the List Package screen, i get the error below. I haven't found any other mention of this so far. Anyone else seen this error or have suggestions?
View 20 Replies
View Related
Sep 18, 2006
Hi,
I am using the SQL Package Installation Wizard to deploy my SSIS packages on to a 64-bit SQL Server and I am getting this error, Library not registered. I am also getting the same error when I tried to import a SSIS package from a 32-bit SQL Server. I was able to save my SSIS packages to the 64-bit SQL Server one by one from Visual Studio. My server is run Windows 2003 Enterprise x64 with SP1, and SQL 2005 Enterprise x64 with SP1 and hotfixes. 64-bit .Net Framework is also registered on the machine.
This is the error from the installation log file:
Exception details: Microsoft.SqlServer.Dts.Runtime.DtsTaskException: Library not registered.
---> System.Runtime.InteropServices.COMException (0x8002801D): Library not registered.
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)
Thanks in Advance.
View 3 Replies
View Related
Jan 14, 2006
How to add SQl statements to the package created by Export Data wizard? I need to add SQL coming from file, the flow would be like this:
1) SQL would drop all objects: (views, tables, stored procedures) etc
2) SQL would create all objects: (views, tables, stored procedures) etc
3) Export Wizard SSIS package would execute
Also is there a dynamic way to add more tables do the package once created in SQL database? I would like to put the whole task on a scheduler too...
View 6 Replies
View Related
