Linguring SPIDS

SQL Server 2000

Just curious - was wondering why some SPIDS are left hanging out there
for up to several weeks. There are no errors or anything. It looks like
normal processing.

Thanks,

Craig(csomberg@.dwr.com) writes:
> SQL Server 2000
> Just curious - was wondering why some SPIDS are left hanging out there
> for up to several weeks. There are no errors or anything. It looks like
> normal processing.

Without seeing the output from sp_who2 or similar, it's difficult to
say much useful. But if they are spid < 50, they are system processes.

If they are > 50, they are user processes, and apparently the client
that opened this connections are still clinging to them. The hostname
and prog_name columns in master..sysprocesses may give some clues.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Lineage ID Errors

I am running an SSIS package and I keep getting this error when it gets to a the dataflow task. I have a bit of an idea of what it means, but I can't figure out how to fix it. IF anybody could explain this error and fixes for it that would be of immense help. Thank you.

Error: 0xC004701C at Load Server Security, DTS.Pipeline: input column "Server" (1434) has lineage ID 1421 that was not previously used in the Data Flow task.
Error: 0xC004706B at Load Server Security, DTS.Pipeline: "component "OLE DB Destination 1" (1420)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".
Error: 0xC004700C at Load Server Security, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Load Server Security: There were errors during task validation.The first error simply says that you have a column in the data flow, Server, that isn't used.

The second error looks to me like there were database changes to that table and now the OLE DB destination needs to be updated. Double click on the OLE DB destination and select the mappings tab. If no changes need to be made, simply click OK.|||

Possible reason could be if your destination table structure or the column data type changed.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=102011&SiteID=1

Thanks

|||You should have a triangle with an exclaimation mark on it. Double click on that component and then mappings, if applicable, to fix it.