1

Topic: SSIS - the Packet is successfully fulfilled but happened nothing

All greetings, at me as not  .
Situation following.
Has been developed Workflow which without problems works in DEV and QA systems.
On PROD to system  Workflow does not work, to be exact - after successful end of the process executable Job Agent, the DB does not contain anything. To put it briefly, the system considers "No news are good news".
About most Workflow.
- There is a loading of the data from several CSV-files in a database.
- On the basis of the loaded data,  Workflow produces analytical calculations then n the amount CSV of documents,  different statistical results is preempted.
I can not understand the reason on which in DEV and QA the arrived files become normally engrossed in reading and in PROD is not present.
And the most interesting that if some times to rename CSV documents SOMETIMES happens  and all becomes engrossed in reading and fulfilled as it is required.
With old files which were used in due time for the first development, also there are no problems if them to give on  in PROD.  problems from executor Job who from file system reads out the data, in my understanding are not present.
On  SSIS in the enterprise   administrators help unfortunately could not also all that I found in the Internet  on this subject,  or the insufficient rights or incorrectly set  . On it if who faced a such problem, share the decision if that exists.
All certainly thanks for the help in the decision!

2

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Vi;
SSIS broad gulls conducts, look there
Or launch a packet from a Visual Studio, see process visually

3

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Thanks for the answer.
Unfortunately in it all and a problem.
As I in a subject title specified, all is fulfilled with success, but without result.
In broad gulls on the server, it costs nothing that could specify me an error.
Tried also full Loging in most Workflow, with its output as a file.
The broad gull comes to an end after  elements (taks) in the packet.  performance something does not reach at all.

4

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Vi;
The packet is fulfilled on behalf of the SQL Agent security account, check up the rights. Or adjust "to fulfill from a name" in step section "in addition".

5

Re: SSIS - the Packet is successfully fulfilled but happened nothing

If to launch in a Visual Studio counters of the data on each branch date  at first are shown. Secondly it is possible to adjust for a branch date the viewer and to look what data there get.

6

Re: SSIS - the Packet is successfully fulfilled but happened nothing

@Vladislav Kolosov
Thanks for council, but packet are already fulfilled from a name  the user who has is right enough.
As I in an initial post wrote, sometimes if to be played with renaming of a title of files all starts to work in "the magic image" without problems. But it works not always and why works too not clearly.
There was an assumption that with files  not so, but they  are processed by systems DEV and QA.
To  system PROD has been adjusted by analogy of system QA.

7

Re: SSIS - the Packet is successfully fulfilled but happened nothing

@bideveloper
Unfortunately from a Visual Studio at me it does not turn out to launch process, on  it will happen on behalf of my user who is not authorized  to write in PROD a database. It unfortunately not to change, on  rules at the enterprise are that.
On it also has been created DEV and QA machines where it was possible  operation of a packet both from a Visual Studio and from automated task Job Agent.

8

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Vi wrote:

All greetings, at me as not  .
Situation following.
Has been developed Workflow which without problems works in DEV and QA systems.
On PROD to system  Workflow does not work, to be exact - after successful end of the process executable Job Agent, the DB does not contain anything. To put it briefly, the system considers "No news are good news".
About most Workflow.
- There is a loading of the data from several CSV-files in a database.
- On the basis of the loaded data,  Workflow produces analytical calculations then n the amount CSV of documents,  different statistical results is preempted.
I can not understand the reason on which in DEV and QA the arrived files become normally engrossed in reading and in PROD is not present.
And the most interesting that if some times to rename CSV documents SOMETIMES happens  and all becomes engrossed in reading and fulfilled as it is required.
With old files which were used in due time for the first development, also there are no problems if them to give on  in PROD.  problems from executor Job who from file system reads out the data, in my understanding are not present.
On  SSIS in the enterprise   administrators help unfortunately could not also all that I found in the Internet  on this subject,  or the insufficient rights or incorrectly set  . On it if who faced a such problem, share the decision if that exists.
All certainly thanks for the help in the decision!

1. SSIS is a curve crutch for poor.
2. The thesis amusing: "With old files which were used in due time for the first development, also there are no problems,".
3. And if to fill old files with the new content?

9

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Vi wrote:

About most Workflow.
- There is a loading of the data from several CSV-files in a database.
- After successful end of the process executable Job Agent, the DB does not contain anything.

Vi wrote:

Tried also full Loging in most Workflow, with its output as a file.
The broad gull comes to an end after  elements (taks) in the packet.  performance something does not reach at all.

well your packet means anything and does not read
Find normal  on  which for "beer" looks at your packet
Otherwise this all guessing on a thick

10

Re: SSIS - the Packet is successfully fulfilled but happened nothing

aleks222 wrote:

1. SSIS is a curve crutch for poor.

the pro and on a crutch skips away further many about two feet... smile

11

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Vi wrote:

@bideveloper
Unfortunately from a Visual Studio at me it does not turn out to launch process, on  it will happen on behalf of my user who is not authorized  to write in PROD a database. It unfortunately not to change, on  rules at the enterprise are that.

If you do not have rights only on record in , and on files is. That instead of record in  can be delivered temporarily a stub (the task which does nothing). And to look that goes on this stub.

12

Re: SSIS - the Packet is successfully fulfilled but happened nothing

Vi;
Literally one of these days saw just the same...
The problem was in a wrong way to files. The way was stored in parameter which used Connection Manager.
Strange  that SSIS does not report about the such

13

Re: SSIS - the Packet is successfully fulfilled but happened nothing

[spoiler ]

aleks222 wrote:

1. SSIS is a curve crutch for poor.

Tell what  use instead of SSIS? [/spoiler]

14

Re: SSIS - the Packet is successfully fulfilled but happened nothing

aleks222 wrote:

1. SSIS is a curve crutch for poor.
2. The thesis amusing: "With old files which were used in due time for the first development, also there are no problems,".
3. And if to fill old files with the new content?

1. It is excessive polemic. The situation is such what it is and .
2. The irony is strange, but  - observations were those.
3. It is possible to try, but unless only for the sake of . For automation it is impossible to name it the constant decision. Especially as already was me  that on DEV and QA all works as it is necessary.
If to you it is not difficult, give in essence or refrain from  if to you this subject delivers hostility.

15

Re: SSIS - the Packet is successfully fulfilled but happened nothing

[quote = _ human] the Way was stored in parameter which used Connection Manager.

.  was not. The wrong way has been registered in adjustments ForEach of the container