Check the owner of the job(s) in querstion. It may be owned by an SID that does not resolve to a valid login which could be giving SMO heartburn.

SELECT ...

Yes, index reorganization can cause a lot of I/O depending on how much work the reorganize decides it needs to perform to organize the index. They do not cause long-running...

Is this what you mean?

How to: Use Values of Parent Variables in Child Packages

Nope. The decision by the engine to use one index or another to satisfy a query will not change the contents of the resultset. The order of the resultset is...

In addition to object ownership within a database make sure the login does not own any databases themselves or any Agent jobs.

SELECT *

FROM sys.databases

WHERE ...

You're welcome. Thanks for the feedback.

Did you stop and start the SQL server service?

Please post the exact "invoked by" text from job history (with sensitive domain or user names masked of course).

Also, look for jobs that might kick off the job in question...

Those are some pretty basic requirements. What have you tried so far?

It sounds like you are simply looking for a tutorial on how to use the Fuzzy Lookup Transformation....

Thong, tha thong thong thong

Indeed they have 🙂 You could always check the SID for the login on the source system and check it against your dev instance. You...

It is safe to use the dropserver/addserver method. All that does is change the underlying entry available in sys.servers.

SELECT * FROM sys.servers WHERE is_linked = 0

Seriously though, just change the destination table to have NVARCHAR instead of VARCHAR and you should be fine.

Welcome to working with Excel using SSIS 🙂

It's not required for NT logins provided they are on the same domain. The SID in that case comes from AD which is not going to change from one SQL...