Hi,
I am testing some import validations on dry run data that has been
deliberately seeded with incorrect values to test the systems. The format of
the data being imported is text length 2 and the field the data is being
imported into is varchar(1). I had been expecting the DTS (SQL 2000) import
to fail however the import completed without error and appeared to be
successful but the data instead of being imported as 2C is being shown as 2.
How can I resolve this issue so that an error is thrown up otherwise I will
have no way of knowing that incorrect data has been imported?
Thanks.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.

On Jun 9, 2:11 pm, billyfix <billy... (AT) discussions (DOT) microsoft.com>
wrote:
Hi billyfix, i'm not sure to have understood very well. Did you use a
cast or convert before import? That's really strange i believe that
when a sql command after an implicit conversion must truncate a field,
it should stop and end up with an error.
Apart this, if you want to get an error when the data length is 2 or
more then you can test it with a LEN function in T-SQL. Build a simle
script with an if statement that raise an error when the condition is
met (i.e. LEN(yourfield)>2). You can then use workflow precedence
constraints (OnFailure and ONsuccess) to build different outputs.

Bye,
M.