Mysteriously dropped rows using Data Flow Task

I'm using the Data Flow Task to load data from a flat file into a SQL table and I'm missing rows. And there doesn't see to be any consistent or obvious reason why.

When I use the Bulk Insert Task I import the correct number of rows from the flat file. But when I use the Data Flow task and use a Flat File Source connected to a OLE DB Destination I get about 1/3 the right number of rows. So looking at these loaded tables at the same time I notice that the Data Flow Task method just skips rows sometimes.

Why does this happen?

Try to enable error output and redirect the error output to a different table and see if any rows are sent there.

Hope this helps,

Ovidiu Burlacu

|||

just for people looking around; this issue got addres in other post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=884012&SiteID=1

Rafael Salas

Mysteriously disappearing stored proc

Hi,
I have an issue with a stored procedure that is disappearing periodically.
It is called from the Agent every minute, and runs just fine for long
periods of a time, often more than a w at once. Then the stored
procedure will be deleted and I will see an entry in the event log for every
time the agent calls it that the stored proc is missing.
It is always the same stored proc. There is another stored proc that also
runs once per minute, and it is never missing.
Does anyone have a clue as to what could cause this, or perhaps some
recommendations for troubleshooting steps I can take in order to find this
out.
Thanks!
Ray ReavisSounds like someone's playing an april fools gag on you.
Response from Microsoft: "It's a feature!"
Sorry, couldn't resist... ; )
"Ray Reavis" wrote:

> Hi,
> I have an issue with a stored procedure that is disappearing periodically.
> It is called from the Agent every minute, and runs just fine for long
> periods of a time, often more than a w at once. Then the stored
> procedure will be deleted and I will see an entry in the event log for eve
ry
> time the agent calls it that the stored proc is missing.
> It is always the same stored proc. There is another stored proc that also
> runs once per minute, and it is never missing.
> Does anyone have a clue as to what could cause this, or perhaps some
> recommendations for troubleshooting steps I can take in order to find this
> out.
> Thanks!
> Ray Reavis
>
>|||Ray Reavis wrote:
> Hi,
> I have an issue with a stored procedure that is disappearing
> periodically. It is called from the Agent every minute, and runs just
> fine for long periods of a time, often more than a w at once.
> Then the stored procedure will be deleted and I will see an entry in
> the event log for every time the agent calls it that the stored proc
> is missing.
> It is always the same stored proc. There is another stored proc that
> also runs once per minute, and it is never missing.
> Does anyone have a clue as to what could cause this, or perhaps some
> recommendations for troubleshooting steps I can take in order to find
> this out.
> Thanks!
> Ray Reavis
Some process is obviously dropping the procedure. What user accounts
have rights on the database to drop the procedure? I wouldn't think too
many processes have admin rights or DROP PROC rights on the production
server.
David Gugick
Imceda Software
www.imceda.com|||Yeah, I agree with David. Use Profiler to find the statement dropping
the SP. You may take the stored procedure "create date" as a hint if
the sp is being dropped and recreated.
Aramid
On Wed, 6 Apr 2005 21:08:37 -0400, "David Gugick"
<davidg-nospam@.imceda.com> wrote:

>Ray Reavis wrote:
>Some process is obviously dropping the procedure. What user accounts
>have rights on the database to drop the procedure? I wouldn't think too
>many processes have admin rights or DROP PROC rights on the production
>server.|||David,
Thanks for the tip. I'm not a dba so some of these things don't come
naturally to me. I'm using the profiler to run a trace on all object
deletions, so hopefully that will turn something up.
As far as permissions are concerned, I don't see a place in SQL2000 where it
specifically shows DROP PROC rights. I looked on the permissions of the
database itself and saw Create Proc rights, but couldn't find drop proc
rights. I'm not sure how much that would help anyway since my company
doesn't have control over this server. We're using windows authentication
rather than SQL Server accounts so I presume administrators on that server
will have those permissions.
Thanks,
Ray
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:u#peO5wOFHA.3704@.TK2MSFTNGP12.phx.gbl...
> Some process is obviously dropping the procedure. What user accounts
> have rights on the database to drop the procedure? I wouldn't think too
> many processes have admin rights or DROP PROC rights on the production
> server.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Ray Reavis wrote:
> David,
> Thanks for the tip. I'm not a dba so some of these things don't come
> naturally to me. I'm using the profiler to run a trace on all object
> deletions, so hopefully that will turn something up.
> As far as permissions are concerned, I don't see a place in SQL2000
> where it specifically shows DROP PROC rights. I looked on the
> permissions of the database itself and saw Create Proc rights, but
> couldn't find drop proc rights. I'm not sure how much that would
> help anyway since my company doesn't have control over this server.
> We're using windows authentication rather than SQL Server accounts so
> I presume administrators on that server will have those permissions.
Create Procedure rights should do it. As far as permissions, they are on
the SQL side, even with Windows Authentication.
This will show you everyone (excluding administrators and other
fixed-server roles who may have inherent rights) who have explicit
rights to create procs.
select user_name(uid) as "Has Create Proc Rights", * from
dbo.sysprotects
where action = 222 -- create proc
and protecttype != 206 -- Deny
David Gugick
Imceda Software
www.imceda.com|||"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:#YL3RW4OFHA.688@.TK2MSFTNGP10.phx.gbl...
> Ray Reavis wrote:
> Create Procedure rights should do it. As far as permissions, they are on
> the SQL side, even with Windows Authentication.
> This will show you everyone (excluding administrators and other
> fixed-server roles who may have inherent rights) who have explicit
> rights to create procs.
> select user_name(uid) as "Has Create Proc Rights", * from
> dbo.sysprotects
> where action = 222 -- create proc
> and protecttype != 206 -- Deny
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
Thanks! I've saved that query in my bag-o-tricks folder. It didn't return
any rows, which is not a surprise. I suspected it was all built-in accounts
that were doing the dirty deed. So far it's been two days since the last
missing sp. I'll be satisfied if it stops but it will kill me to not know
what is going on.
We have the same software running at a lot of businesses nationwide with no
problems such as this -- only this one customer has this issue. It makes us
look bad if we can't prove what is going on even when we're pretty certain
it's not our code causing the problem.
-- Ray

Mysteriously changing datetime data

I know this may seem like a weird thing, but today something very strange
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
David Portas
SQL Server MVP
--|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?

Mysteriously changing datetime data

I know this may seem like a weird thing, but today something very strange
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
--
David Portas
SQL Server MVP
--|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?

Mysteriously changing datetime data

I know this may seem like a weird thing, but today something very strange
happened to one of my database tables. The table has three columns that are
of type datetime. They normally contain values such as 08/12/2004 16:03:35.
One of the three columns, however, now shows either 08/12/2004 only or
08/12/2004 00:00:00. The other two columns are still "normal".
No update queries have been run against this table.
Does anybody know why the dates would have changed like that?
DATETIME columns don't contain any inherent format and they always include
both date and time. It looks like your client application, whatever that may
be, is formatting the date differently to what you expect. Check the
regional settings on your PC or any other options in your app that may
affect date formatting.
David Portas
SQL Server MVP
|||Where are you looking, in Enterprise Manager? Try using SELECT cols FROM
table in Query Analyzer.
http://www.aspfaq.com/
(Reverse address to reply.)
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?
|||Hi SackerMan
The values actually stored in a datetime column don't 'look' anything like
what you have shown us. They are stored in an internal unambigous format
that you never see.
How a datetime value 'looks' depends on the tool and the command you use to
display it.
So, how are you actually seeing these values?
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"SackerMan" <SackerMan@.discussions.microsoft.com> wrote in message
news:6529C05A-2374-421C-93C4-6A498163F365@.microsoft.com...
> I know this may seem like a weird thing, but today something very strange
> happened to one of my database tables. The table has three columns that
are
> of type datetime. They normally contain values such as 08/12/2004
16:03:35.
> One of the three columns, however, now shows either 08/12/2004 only or
> 08/12/2004 00:00:00. The other two columns are still "normal".
> No update queries have been run against this table.
> Does anybody know why the dates would have changed like that?

Mysterious Sql2000 process blocking

I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.
Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.co...prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>

Mysterious Sql2000 process blocking

I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.com/sf_block_prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>

Mysterious Sql2000 process blocking

I have made several posts regarding my sql2000 cpu mysteriously staying at
100% for 10 minutes at a time. Using a performance monitor, I finally
noticed that during these times there is a sql process that is blocking the
others and causing some kind of "race" condition. The blocked processes
time out, but the blocking process seems to stay blocked often until the
service is restarted. It seems like sql should not allow this. I have not
been able to find out the cause or statements that produced the problem.
The only application using the sql server is an ASP.NET application that
uses 100% stored procedures (no dynamic sql). Does anyone have any
suggestions for finding the cause of process blocking like this? Thanks.Dan,
You'd have to examine the code to determine this.
These may help:
http://www.sql-server-performance.c..._prevention.asp
and
http://www.support.microsoft.com/?id=224453
and
http://www.support.microsoft.com/?id=271509
and
http://support.microsoft.com/?id=224587
and
http://support.microsoft.com/?id=243589
and
http://support.microsoft.com/?id=243588
HTH
Jerry
"Dan English" <dan_english2@.cox.net> wrote in message
news:eUAAmR4zFHA.2960@.tk2msftngp13.phx.gbl...
>I have made several posts regarding my sql2000 cpu mysteriously staying at
>100% for 10 minutes at a time. Using a performance monitor, I finally
>noticed that during these times there is a sql process that is blocking the
>others and causing some kind of "race" condition. The blocked processes
>time out, but the blocking process seems to stay blocked often until the
>service is restarted. It seems like sql should not allow this. I have
>not been able to find out the cause or statements that produced the
>problem. The only application using the sql server is an ASP.NET
>application that uses 100% stored procedures (no dynamic sql). Does anyone
>have any suggestions for finding the cause of process blocking like this?
>Thanks.
>

mysterious restore

I am a support rep for an app running on SQL Server 7 sp3.
The customer had a table mysteriously restored along with the dependencies [sp.s, indexes, etc] for that table.
Is there any logging in sql server that will show when tables or objects have been dropped, recreated or restored?
thanksLook up the msdb..restorehistory table.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"tlr" <anonymous@.discussions.microsoft.com> wrote in message
news:86C067AA-72E8-49CD-A34A-1E79E4E03315@.microsoft.com...
I am a support rep for an app running on SQL Server 7 sp3.
The customer had a table mysteriously restored along with the dependencies
[sp.s, indexes, etc] for that table.
Is there any logging in sql server that will show when tables or objects
have been dropped, recreated or restored?
thanks