Is there any table where we have source connection and destination connection information about the DTS packages?
None of these tables in the msdb have this information.
1) sysdtscategories
2) sysdtspackages
3) sysdtspackagelog
4) sysdtssteplog
5) sysdtstasklog
6) sysdtspackages90
7) sysdtspackagefolders90
8) sysdtslog90
Regards,
Ashish Johri
I have a question regarding Raw Files. I am breaking a large package into more modular components for better processing and debugging.
The process will start with a preparatory dataflow that will create a Raw File(s). This Raw File will then be used as the source in possibly 6 data flows and/or packages.
My question is whether 1 Raw File can be read concurrently by the multiple jobs and how this would affect processing. I'm assuming that this would slow processing.
My other option is to Multicast the writing of the Raw File to 5 other versions of the file. All would be identical except for filename. Obviously this would use more disk space but this is not a concern as we have lots of disk space. Our concern is for speedy processing.
If you have experience with Raw Files, please let me know how you approached this issue. As always, blogs and specific examples are always great!
Thanks in advance.
Hi,
doing my first steps in SSIS I wanted to copy data from 2 different SQL 2000 database servers to a SQL 2005 Data warehouse. For not having to deploy additional views and procedures to the individual systems I chose to create a Data Source View to create an abstract view on the different data sources. I found out that I can have named queries pointing to the two different data sources in the same view.
1 Project, 2 Data Sources, 1 Data Source View with 3 Named Queries
When I now add a Data Flow Task to the Control Flow how can I specify my DSV as Source for Transformations? I even added both OLEDB Connections to the Connection Manager but the Named Queries from my DSV do not appear at all. I even tried "SELECT from [myNamedQueryFromDSV]" but without success.
The description available at http://msdn2.microsoft.com/en-us/ms403395.aspx is bullshit. There is nothing to expand about the "Connection Manager" in the Data Flow Window. I can add a OLEDB Source as described in the above HOWTO and double click it. But the dropdown field for Connection Manager does offer only the two OLEDB Connections and nothing more. Among the items of the access mode "Tables and Views" the named queries not appear. It does not even work with a homogeneous Data Source View.
How can I make it work? Ain't there a better (working) HOWTO out there on how to enable DSV als Data Flow Task data sources? Do I have to wait for SP2 to solve the problem or is it not possible by intention?
Cheers,
Frank
I have a Rounding error: Between flat file connection manager Source & OLE DB Connection Destination (SQL Server 2005) in my Dataflow.
File looks like this lets call column names Col A,B,C,D
70410000 RD1 1223631.92 196042.42
70329000 ICD 11025.84 3353.88
71167300 COL 104270.59 24676.96
flat file connection manager settings: first row Column names then Advanced tab Col A float , Col B float , Col C string ,Col D float ,
OLE DB Connection Destination (SQL Server 2005)
CREATE TABLE [dbo].[PT_CUST_ABR](
[PARTY_NO] [float] NULL,
[PARTY_NAME] [varchar](75) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[TELECOMABR] [float] NULL,
[GENIABR] [float] NULL,
Problem: ColA (Source) Rounding error to PARTY_NO (Destination)
I have a field of text of in a flat file that the flat file connection manager Source picks up correctly €œ70000893€?
However when it gets the OLE DB Connection Destination the data has changed to 70000896. That€™s before its even Written to the database.
The only clue that something is wrong in the middle is the great Data viewer shows the number as 7.000009E+07
Other clues looking at the data it appears there is a rounding error on only the number that dont end in 00
ColA (Source) PARTY_NO (Destination)
71167300 71167296
70329000 70329000
70410000 70410000
Any ideas people?
Thanks in advance
Dave
Hello,
I've created a SSIS Solution and have created Data Sources. I have two packages. One was created before the Data Sources, and one was created after. The package that was created after is using connections from the Data Sources. I want to change the package before the Data Soruces were created to use them, but when I right click in the Connection Managers pane "New Connection From Data Source.." is not an option.
Did I not add it to the Solution properly?
How do I get it to show?
Did I not refresh something?
Please provide the how if you figure it out.
Thanks
I came across something strange today. I was wondering I was doing something wrong.
View 7 Replies View RelatedI have created a integration services project on machine A and have added to visual source safe 6.0
When i try to take the project from source safe and store that on a different machine B i have a problem with it....
I check in everything on Machine A
When i try to add on machine B it tries to add it with "Name of package(1)" which means that its adding a copy.But it dosent do for all only for few
Could anyone let me know what the problem is??????
My source files are in C:Process folder. File names are in the format proc*.csv
I am using foreach loop container to iterate over the files in folder "C:Process"
I have a user variable "filename"
The order of my tasks
ForEach - Data Flow task - File System Task
In Data Flow task, I have ole db source which should take the dynamic filename from user variable "filename". whats happening is when i give fixed filename, without foreach loop container the package is working fine.
with dynamic filename, I am not able to run the package because of ole db source Error - cannot aquire connection from connection manager.
Thanks for u'r help.
We want to use a single connection manager in different packages. IS there a way to do it? We tried copying the same connection manager in different package, but it makes a copy of the same in different package, so any change in the connection manager doesnt gets reflected in other package.
IS there a way to make all the different packages use the same connection manager?
I have set up a new connection as a connection from data source, but I cannot see how to use this connection to create my Data Flow Source. I have tried using an OLE DB connection, but this is painfully slow! The process of loading 10,000 rows takes 14 - 15 minutes. The same process in Access using SQL on a linked table via DSN takes 45 seconds.
Have I missed something in my set up of the OLE DB source / connection? Will a DSN source be faster?
Thanks in advance
ADG
I am trying to run a package outside of the Business Intelligence development Studio. It continuously fails and tell me that my username cannot logon due to a password failure. When I check my connections the password never shows in the connection string and remains blank in the connection properties although I have checked Save Password in the connection properties. Does anyone know how I can save the password in the connection string being utilized in the SSIS package?
View 3 Replies View RelatedHi, experts here,
I found a very strange problem with the OLE DB connection in SSIS package though.
What happened was when I set the connection type to be OLE DB, whenever I declare a package variable it still gives me the error saying: please declare the scalar variable.
Once I changed the connection type to be ADO.NET, then it works fine.
Why is that? Anything wrong with OLE DB connection?
Looking forward to hearing from you for any ideas on it.
Best regards,
Hi,
I created a COM-visible .NET class that I want to use to run my SSIS packages. I did this so that I could store variables, connection strings and other options in a central database and have my class set the appropriate connections and variables in the packages and then run them and also log all of my package logging to one central database as well.
I got one package to work in this setting (the package used an ADO.NET connection to call a couple of stored procedures and an SMTP connection manager as well as 10-15 user variables). However my second project is not working when I call it using my .NET class (it works if I manually run the package from SQL Server). When I check my logging it says that it is encountering this error ("SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "INFERNO.Wyethport.Wizard+NET" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.") The only other error message that I get is ("component "OLE DB Destination" (1785) failed validation and returned error code 0xC020801C.")
I have set up my packages to save sensitive data with a password and my .NET class sets the password before loading and executing the package so it isn't that problem. Does anyone have any ideas? This has become increasingly frustrating as I don't feel like I understand the goals and concepts behind SSIS security so I am not sure that I am even attacking the problem correctly.
Thanks,
Jeff
Scenario:
130 dtsx packages using 4 matching connections.
3 of those connections are stored in an SSIS Configuration table in an Operational database.
The last connection is in a shared data source and points to the Operational database so the packages can grab the others.
Problem:
It's time for deployment and all of those connections must change to production servers.
The 3 are no issue, just change the ConfiguredValue in the SSIS Configuration table on the production box to point to the other production servers.
However, the fourth one... I had made an assumption that when you changed a shared data source it filtered down throughout all the packages. We all know what assumptions do to you.... So. I need a way to change all 130 connections (and be able to change ALL packages quickly and simply for other projects in the future)
Solution:
It has been suggested that we use another package to run though all of the packages and change the connection with a script task. I can live with this (and more importantly so can our DBS's who have to deploy).
I have one snippet of code to ADD a connection using a variable holding the connection string, but we dont' want to add one, just change an existing one.
Has anyone else done this? Or had a similar problem and way to fix?
We are likely to have many projects in which the connections MUST change at deployment, and the idea of going into every package to make the change is sad at best... We would be more likely to move back to a competitor's product that has a connection repository, than continue with SSIS.
Ches Weldishofer
ETL Developer
Clear Channel Communications
Today I was making a few reports.
When I tested the reports in Visual Studio, they worked great: I got the expected result.
But when I deployed the reports to our reportserver the problem started.
When I click on the directory in which my reports are deployed, I got my 4 reports.
Till now everything worked correct.
But when I click on a report to view the results it went wrong.
I got an error:
"Cannot create a connection to data source 'Live'"
(Live is the name of our data source).
We are using the Windows Logons and I am sure that I have all the rights on the server, I gave myself 'sysadmin' rights, so it should work.
I also have tried it with all the roles assigned on my account, but then it still won't work.
When I modify the data source, and set it to another server en database it works.
The datasource 'Live' exists on a x64 MsSQL server, en the other datasource is on a x86 MsSQL server.
Maybe that is the problem?
Can someone tell me what is wrong?
Hi,
I have a table need to export to excel. 3 columns are 4000k. I can create the ssis package by using import and export wizard and it works fine. But when I try to edit the destination connection for excel, like using another excel file. In the edit window, the Name of the Excel Sheet box is empty, I click new button. It always fail. (with the 3 columns created as varchar (4000) or nvarchar(4000).
I am wondering how import and export wizard can create this table which I can't create it manually?
Thanks
I have deployed to production a number of nested packages (parent packages that call child packages) to the SQL msdb via the Save As option rather than building a deployment utility. These packages reference configuration files in a static location off of the c: drive on the production server. In the development environment, when connection changes are made and I run the Reload with Upgrade option the connection manager takes on the new server and user id settings. However, out on the production side I get the following error from the SQL job log:
Cannot load the XML configuration file. The XML configuration file may be malformed or not valid.
As a result the SQL job uses the default connection information which references the development database rather than the production database. I did research the error but found no good solutions. Is there a way to ensure the configuration files are formed correctly and that the packages are correctly referencing the configuration files? We are trying to run the ETL updates via a SQL job.
Any suggestions? Thanks.
T
every time we develop new dts and move it to production we have to MANUALY
modify data source.
I can submit data source as input parameter to dts and using global variable assign it connection data source.
Could it be done at run time ?
Example
if dts start on dev1 server all
connections points on dev server
if dts starts on prod server all
connection point on prod
Thank you
Alex
Hi all,
I am trying to view report that i deployed to reporting service but when i try to view it, it gives error:
An error has occurred during report processing.
Cannot create a connection to data source 'INVC'.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
the datasource is ODBC
For seting up the connection should we use Connection Manager or New Connection From Data Source?
The advantage of using Data Source is that we have the connection avalilable at project level but I've studied it somewhere that Data Source is used for SSAS not SSIS.
But I don't have enough explanation to give it to my team, that why I am not using Data Source.
We are working on VSS, do we have to reset the connection managers if want to test our packages on some other machine(else than the one on which it was developed)?
Hi,
When I view a report, I get the error message:
An error has occureed during report processing.
Cannot create a connection to data source "data source name"
Cannot open database "database name" requested by the login, The login failed, Login failed for user "username".
The data source will connnect to my OLAP server and I believe I have right to access the OLAP server.
Why the error occurred? Somebody can help me? Thanks very much!
Hi,
I was trying to connect to Oracle Source in SSIS
1. Err: Test connection failed because of an error in initializing provider. Oracle Client and networking components were not found
Sol: I installeed the Oracle Client tools
2. Err: ORA -12154: TNS: Could not resolve teh connect identifier specified
Sol: Then I point out the TNS file
3. Now I coonect the Oracle db . I go to Connection Manager . Specifies the provide as: Native OLE DB Oracle Provide for OLE DB, Select my DB, provide teh user name and password. and check if the connection passed.
Then in my data Flow Task when I add this source and check the Colmns its gives me an error./ sort of warning
The component reported the following warnings:
Warning at {C947B.......} [Ole DB Source[1]]: Cannot retrieve the column code page info from the OLE DB provider. if the components supports teh "DefaultCodePage" property, the code page from that property will be used.....
Will this warning has an significance. i dont see any error in my output data. but is there something I m doing wrong.
4. When I set my ProtectionLevel under Security in package property to "Dont Save Sensitive" in order to easily configure the package I m getting this error: failed Validation. The default one was EncryptSensitiveWithUserKey then its running smoothly.
Can somebody advice me on this?
I addded the all the errors and solution for 1 and 2 becuase in that way this will be helpful in future.
help - I€™ve been stuck on this for days.
My software vendor limits the sessions to one (1) per log-in to Oracle 9i and I€™m having tons of problems trying to extract data through an SSIS package. Everytime I run the package SSIS already logged in and the OLE DB source fails because of the sessions exceeded error.
Is there any way to limit the connection to just when I need the data to pump across on the OLE DB source?
Thank you very much for any help.
Regads,
Nestor
Hi all,
I don't really understand the difference between the "data source" and the "connection manager" in a SSIS solution.
I tried to create a data source (if I understood correctly, I will ba able to share that connection between all packages in the solution), then I create a new connection manager inside a package. But when I make a modification in the data source, nothing change in the connection manager ?!!?
What I think is that when I'm making a new connection manager, what's really happen is a copy of the data source, is that correct ? If it is I dont't understand the avantage of making a new data source ....
Thanks for your response
Why is it that sometimes I get this error and sometimes not after I deploy the same shared data souce to my Report Server?
Even if I try deleting the datasouce through Report Manager the redeploy it from VS 2005, it still errors out when I run my report. I am able to run my report fine in VS.
An error has occurred during report processing.
Cannot create a connection to data source 'mydatasourcenamehere'.
For more information about this error navigate to the report server on the local server machine, or enable remote error
I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?
I'm pulling my hair out at this point:
Screen Shots:
http://www.webfound.net/datasource_connection.jpg
http://www.webfound.net/datasource_connection2.jpg
http://www.webfound.net/datasource_connection3.jpg
Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run
An error has occurred during report processing.
Cannot create a connection to data source 'datasourcename'.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Hello everyone,
I posted the same issue before, but I couldn't find the solution yet. I am posting this agian cos I tried almost everything and I am not able to solve the issue.
Let me explain what is happening here:
Server A - is my development local machine
Server B - is the remote reporting server, where all reports are deployed
Server C - is where the databases are located
- After successfully deploying the project (the reports and datasources) on the remote server and try to run the report , I am getting the following error message
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'dsCallB'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
- I tried to deploy and run the same report on my local machine report server(Server A), which is still accessing the same database from Server C. This works fine.
So from this we can understand that A ==> B ==> C is not working, however A ==>C works fine(using Server A as a report server).
I almost tried all the possible solutions that are posted on the forum, such as storing the credential information on the report server (server B), created a data source, which is not a shared data source, on the report server level e.t.c. and I ended up with nuthin.
The weired thing is that there are existing reports that are already created and deployed(by somebody else) in the report server (server B) , which access the database on Server C. These existing reports run with no problem, even I can create a report which uses the existing data source and runs perfectly. However, when I create a new report which uses a different data source (from Server C), and deploy it to Server B and tried to run it, the above error message comes.
Please let me know if you have any idea.
Thx.
Hi!
I've created a project includen 3 reports based on following code on 3 server. The report includes 3 different datasources an 3 different report. All 3 reports are grouped on Database and summerizad zise.
SELECT
SD.name [Database],
SMF.name [File],
SMF.size [Size]
FROM
sys.master_files SMF INNER JOIN sys.databases SD
ON SD.database_id = SMF.database_id
I can run all reports in Visual Studio (preview). But I can only run one the reports after depolying the project! I get this message when I raun the other 2 reports:
An error has occurred during report processing.
Cannot create a connection to data source 'uasql02_datasource'.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
I tried running the report from an server (where reportingservices is installed) finding that all the reports works as they should. I logged in another server with the same credentials. I got same message on the server as I get on my own camputer, "Cannot create a connection to data source ..."
Is there anybody out there having same problem as I, or someone who has any suggestion?
Thanks for any suggestion!
/*
Fari Sah
*/
Everything is set up the way it should be, as far as we can tell.
However, when we drop in a SQL data source and try to configure, it, we
get a blank box for choosing the connection string, and it won't let us
make a new one.
Has anyone encountered this before? If so, how can we fix it?
Can I change databases for a SqlDataSource in code behind and still use the edit,inset,delete capabilities of the SQLDataSource control?
View 1 Replies View Related
I successfully created the a Report model and deployed it to the server. When i run the a simple report on the SQL Server where reporting Services is installed it runs fine. When I run the report from anywhere else, I get the error below. I don't have a datasource called 'dataSource1'.
*******************************************************************
For more information about this error navigate to the report server on the local server machine, or enable remote errors
----------------------------
Cannot create a connection to data source 'dataSource1'.
----------------------------
An error has occurred during report processing.
*******************************************************************
Thanks for any help!
I hope this is a fairly simple problem that I'm just missing. I've installed SQL Server 2005 Developer Edition on Windows XP Professional. I'm trying to create an ODBC data source under an ID I created ("InstallOwner") that is part of the administrators group. In the Wizard, I give it a name and default to the "local" server. I selected to authenticate the ID using SQL Server authentication. However when I enter the ID and Password, I get the following error.
"Connection Failed - SQL State=28000, SQL Server Error: 18456, [microsoft][SQL Native Client][SQL Server] Login Failed for user "InstallOwner". If I use the "sa" account, it works fine. Can someone point me in the right direction?
I have installed Operations Manager on one server and Reporting Services for Operations Manager on another. When I attempt to run reports from Operations Manager, I receive the following message: Cannot Create a Connection to Data Source "DataSource1" Any suggestions?
View 2 Replies View Related