1

Topic: SSIS: the packet from does not work

Hello.
Help to solve a problem please: there is a packet which of the text file copies given in the DB table.
At start from studio and from Integration Services Catalog/SSISDB the packet works.
But if a packet to launch from the job of service of SQL Server Agent writes an error: "Data conversion failed. The data conversion for column" budget "returned status value 2 and status text" The value could not be converted because of a potential loss of data. "."
The field type numeric (18,2), it without conversions goes at once in the field of the table of the same data type.

2

Re: SSIS: the packet from does not work

Very strange
On idea NOT  it to depend
There it is necessary to look under what  the agent is launched - but then the error would be another
In 1 queue I would check up on that most  there is an error
the error looks in
SSISDB.catalog.event_messages
?

3

Re: SSIS: the packet from does not work

Gulin Feodor, I is already almost confident that the reason regional settings at my security account and the controlled auxiliary security account, from under which the service of SQL Server Agent works. I only do not know as to come on the server from under this security account and to check up regional settings.
P.S. The packet is launched with truly tuned adjustments of a surrounding (specially checked up) and an error from own system of the error log.

4

Re: SSIS: the packet from does not work

rsolanov wrote:

Gulin Feodor, I am already almost confident that the reason regional settings at my security account and the controlled auxiliary security account, from under which the service of SQL Server Agent works. I only do not know as to come on the server from under this security account and to check up regional settings.
P.S. The packet is launched with truly tuned adjustments of a surrounding (specially checked up) and an error from own system of the error log.

Likely it is not correct but I  start service under the administrator
On good it is necessary likely minimum rights to produce (or the account)
https://www.mssqltips.com/sqlservertip/ … e-account/
As  it . Whether will quickly check up errors if the agent under the account

5

Re: SSIS: the packet from does not work

That as a result it appeared: at adjustment of regional server options in the security account from under which the service of SQL Server Agent works were not saved and it was necessary to change regional settings of this security account directly in the register. After that the packet successfully earned. But in a packet property LocaleID as Russian has been explicitly exposed. But thus I watched an error, it seemed that it does not work. At the further learning all became clear: copied from other server within the limits of the project of passage to the new server regional settings were as Russian and thus a decimal comma was as a point instead of a comma and in the data of the text file the separator is a point. Therefore Russian localization did not allow to read correctly this file while manually them did not change. But I think it is necessary to estimate volume of operation of change of all packets where this moment takes place that it was possible to correct in regional parameters as a separator whole and a fractional part from a point on a standard comma.

6

Re: SSIS: the packet from does not work

rsolanov;
The standard just a point, forget about a comma;
If the data comes from a comma, you should convert them in a packet on a point

7

Re: SSIS: the packet from does not work

Otherwise you will catch all rake of bugs of localization

8

Re: SSIS: the packet from does not work

wrote:

rsolanov;
The standard just a point, forget about a comma;
If the data comes from a comma, you should convert them in a packet on a point

To read as a line - then  a comma on a point - then  to decimal?

9

Re: SSIS: the packet from does not work

If there are difficulties with adjustment , for example, there are no rights, yes.

10

Re: SSIS: the packet from does not work

wrote:

rsolanov;
The standard just a point, forget about a comma;
If the data comes from a comma, you should convert them in a packet on a point

Strange but by default in Russian localization there is a comma, checked on new computers where OS just installed. It seems to me to change on the server  adjustments  is .

11

Re: SSIS: the packet from does not work

rsolanov;
The alternative - suddenly to obtain the data, which in 100 times more necessary because the separator was not defined
The server version initially is better for putting native, without localization (if there are no certain dop-requirements)