'could not be converted because of a potential loss of data'

I have a FoxPro dbf that includes From Milepost (f_mp) and To Milepost (t_mp) fields. These fields contain values between -1 and 9999.9999.

I don't have FoxPro installed, but when I attach the dbf to Access, I see the fields defined as datatype Double.

I have a SQL table that I'm trying to import the dbf data into. In that table the two fields are defined as datatype Real.

When I execute the task, it fails at the first milepost value with 4 digits to the left of the decimal point.

I read up on datatypes, then redefined the milepost fields as Floats, but nothing changed.

Any ideas or suggestions would be greatly appreciated.

ginnyk

Which component is givng the error message? If it's the OLE DB Source adapter, you can change its output column data type for the milepost fields that would allow a lossless conversion. If you can't find a suitable type, as a last resort, you could try converting the data to string.|||

Ted,

The full error text is:

"[SQL DcsEx [574]] Error: There was an error with input column "t_mp" (646) on input "OLE DB Destination Input" (587). The column status returned was: "The value could not be converted because of a potential loss of data.".

No matter which FoxPro Ex source dbf I use, the task fails at the destination input, on the first record that has a number greater than or equal to 1000...specifically - 1022, 1341.76 and 1002.849. The 4 digits left of the decimal in the erroring field is the only thing the 3 records seem to have in common.

I have other tasks in the same package that convert Fox doubles to SQL real or float numbers, greater than 1000, with no trouble. I am completely stumped and don't know where to look next.

|||

Could you give us more information on what your package actually does with this data. Do you only copy or have some transforms as well? Take a look at data types used in SSIS components for the "t_mp" column.

Thanks.

Could making an extra backup cause data loss?

I'm wondering whether in some circumstances, making an additional SQL backup
could cause data loss.
For ezample, a database is configured with the full recovery model. The DBA,
Alice, has scheduled daily full backups at 0200, and transaction log backups
at 0000, 0600, 1200 and 1800.
Suppose programmer Bob makes an additional full backup at 1000 so that he
can copy the database to his laptop, then removes this backup from the
server and doesn't tell Alice.
What happens if Alice wants to do a restore at 1201? Can she just restore
the 0200 full backup followed by the 0600 and 1200 transaction log backups,
or will there be missing data between 0600 and 1000?
Any comments appreciated. Thanks,
Simon
Hi
A full back does not affect the transaction log sequence as long as you do
not set it to truncate the log also (option when you do it through
Enterprise Manager).
In your case, the full backup contains all the data and the log from 0600,
but does not truncate the log. The 1200 log dump contains the log from 0600
to 1200.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <simon@.antispam.aardvarks> wrote in message
news:419524d5$0$226$bed64819@.news.gradwell.net...
> I'm wondering whether in some circumstances, making an additional SQL
backup
> could cause data loss.
> For ezample, a database is configured with the full recovery model. The
DBA,
> Alice, has scheduled daily full backups at 0200, and transaction log
backups
> at 0000, 0600, 1200 and 1800.
> Suppose programmer Bob makes an additional full backup at 1000 so that he
> can copy the database to his laptop, then removes this backup from the
> server and doesn't tell Alice.
> What happens if Alice wants to do a restore at 1201? Can she just restore
> the 0200 full backup followed by the 0600 and 1200 transaction log
backups,
> or will there be missing data between 0600 and 1000?
> Any comments appreciated. Thanks,
> Simon
>
|||As mike says - the good thing about log backups is that they are not affected
by full backups - if you have the sequence of logs you can restore from any
full backup.
It's important that Bob doesn't do a log backup though as this will cause
problems - even if he uses the NO_TRUNCATE option.
"Simon" wrote:

> I'm wondering whether in some circumstances, making an additional SQL backup
> could cause data loss.
> For ezample, a database is configured with the full recovery model. The DBA,
> Alice, has scheduled daily full backups at 0200, and transaction log backups
> at 0000, 0600, 1200 and 1800.
> Suppose programmer Bob makes an additional full backup at 1000 so that he
> can copy the database to his laptop, then removes this backup from the
> server and doesn't tell Alice.
> What happens if Alice wants to do a restore at 1201? Can she just restore
> the 0200 full backup followed by the 0600 and 1200 transaction log backups,
> or will there be missing data between 0600 and 1000?
> Any comments appreciated. Thanks,
> Simon
>
>

Could making an extra backup cause data loss?

I'm wondering whether in some circumstances, making an additional SQL backup
could cause data loss.
For ezample, a database is configured with the full recovery model. The DBA,
Alice, has scheduled daily full backups at 0200, and transaction log backups
at 0000, 0600, 1200 and 1800.
Suppose programmer Bob makes an additional full backup at 1000 so that he
can copy the database to his laptop, then removes this backup from the
server and doesn't tell Alice.
What happens if Alice wants to do a restore at 1201? Can she just restore
the 0200 full backup followed by the 0600 and 1200 transaction log backups,
or will there be missing data between 0600 and 1000?
Any comments appreciated. Thanks,
SimonHi
A full back does not affect the transaction log sequence as long as you do
not set it to truncate the log also (option when you do it through
Enterprise Manager).
In your case, the full backup contains all the data and the log from 0600,
but does not truncate the log. The 1200 log dump contains the log from 0600
to 1200.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <simon@.antispam.aardvarks> wrote in message
news:419524d5$0$226$bed64819@.news.gradwell.net...
> I'm wondering whether in some circumstances, making an additional SQL
backup
> could cause data loss.
> For ezample, a database is configured with the full recovery model. The
DBA,
> Alice, has scheduled daily full backups at 0200, and transaction log
backups
> at 0000, 0600, 1200 and 1800.
> Suppose programmer Bob makes an additional full backup at 1000 so that he
> can copy the database to his laptop, then removes this backup from the
> server and doesn't tell Alice.
> What happens if Alice wants to do a restore at 1201? Can she just restore
> the 0200 full backup followed by the 0600 and 1200 transaction log
backups,
> or will there be missing data between 0600 and 1000?
> Any comments appreciated. Thanks,
> Simon
>|||As mike says - the good thing about log backups is that they are not affected
by full backups - if you have the sequence of logs you can restore from any
full backup.
It's important that Bob doesn't do a log backup though as this will cause
problems - even if he uses the NO_TRUNCATE option.
"Simon" wrote:
> I'm wondering whether in some circumstances, making an additional SQL backup
> could cause data loss.
> For ezample, a database is configured with the full recovery model. The DBA,
> Alice, has scheduled daily full backups at 0200, and transaction log backups
> at 0000, 0600, 1200 and 1800.
> Suppose programmer Bob makes an additional full backup at 1000 so that he
> can copy the database to his laptop, then removes this backup from the
> server and doesn't tell Alice.
> What happens if Alice wants to do a restore at 1201? Can she just restore
> the 0200 full backup followed by the 0600 and 1200 transaction log backups,
> or will there be missing data between 0600 and 1000?
> Any comments appreciated. Thanks,
> Simon
>
>

Could making an extra backup cause data loss?

I'm wondering whether in some circumstances, making an additional SQL backup
could cause data loss.
For ezample, a database is configured with the full recovery model. The DBA,
Alice, has scheduled daily full backups at 0200, and transaction log backups
at 0000, 0600, 1200 and 1800.
Suppose programmer Bob makes an additional full backup at 1000 so that he
can copy the database to his laptop, then removes this backup from the
server and doesn't tell Alice.
What happens if Alice wants to do a restore at 1201? Can she just restore
the 0200 full backup followed by the 0600 and 1200 transaction log backups,
or will there be missing data between 0600 and 1000?
Any comments appreciated. Thanks,
SimonHi
A full back does not affect the transaction log sequence as long as you do
not set it to truncate the log also (option when you do it through
Enterprise Manager).
In your case, the full backup contains all the data and the log from 0600,
but does not truncate the log. The 1200 log dump contains the log from 0600
to 1200.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Simon" <simon@.antispam.aardvarks> wrote in message
news:419524d5$0$226$bed64819@.news.gradwell.net...
> I'm wondering whether in some circumstances, making an additional SQL
backup
> could cause data loss.
> For ezample, a database is configured with the full recovery model. The
DBA,
> Alice, has scheduled daily full backups at 0200, and transaction log
backups
> at 0000, 0600, 1200 and 1800.
> Suppose programmer Bob makes an additional full backup at 1000 so that he
> can copy the database to his laptop, then removes this backup from the
> server and doesn't tell Alice.
> What happens if Alice wants to do a restore at 1201? Can she just restore
> the 0200 full backup followed by the 0600 and 1200 transaction log
backups,
> or will there be missing data between 0600 and 1000?
> Any comments appreciated. Thanks,
> Simon
>|||As mike says - the good thing about log backups is that they are not affecte
d
by full backups - if you have the sequence of logs you can restore from any
full backup.
It's important that Bob doesn't do a log backup though as this will cause
problems - even if he uses the NO_TRUNCATE option.
"Simon" wrote:

> I'm wondering whether in some circumstances, making an additional SQL back
up
> could cause data loss.
> For ezample, a database is configured with the full recovery model. The DB
A,
> Alice, has scheduled daily full backups at 0200, and transaction log backu
ps
> at 0000, 0600, 1200 and 1800.
> Suppose programmer Bob makes an additional full backup at 1000 so that he
> can copy the database to his laptop, then removes this backup from the
> server and doesn't tell Alice.
> What happens if Alice wants to do a restore at 1201? Can she just restore
> the 0200 full backup followed by the 0600 and 1200 transaction log backups
,
> or will there be missing data between 0600 and 1000?
> Any comments appreciated. Thanks,
> Simon
>
>