BOM not worth it - files just should be consistent. throughout.

likely some files are manually created, and others through some utility - this is normally the case when I get...

think you failed to understand what I intended.

when you create a flat file connection manager you should define it's encoding before opening the file so headers get populated correctly. doing...

that looks like a "UTF-8 with BOM" file being read as non unicode.

ensure you use the correct definition when defining the connector - and fix what generates the file not...

have a look at https://www.sqlshack.com/how-to-discover-and-handle-orphaned-database-users-in-sql-server/

and you also need to consider.

• calls using dynamic SQL - will not show up as dependencies
• SQL Agent jobs - both T-SQL on them, and command line/SSIS packages that...

one way - other is to have the file as a valid SQL Server unicode file - there are quirks about it.

drop table if exists Test2 
CREATE...

what does the SQL Logs say about licensing and allocated cores? Could be limited by license applied.

and what is the VM type - some config there may be wrong -...

you can't do that as far as I know - if you do that deny then db_owner is required - but having the list of db's on SSMS does NOT...

if you read my post and the link I gave you it states what you have to do to address that requirement.

if it is partitioned what matters is if it is has the partition operator on the plan or not - if it has then being partitioned is helping the query...

bump.. page bug

best advise is DON'T use SSIS for this.

Load data from one of the db's into a staging (or even tempdb) and do the merge on the SQL server side.

if you...

why bother sometimes. basic sql stuff that should not need our help.

straight replace -

SET @FILEPATH = replace(@FILENAME, 'chartobereplaced_escapedifneeded', 'replacewith_escapedifneeded')

you can just try out until you get the replace correct -...

If you look at the column headers of the file and compare them to the table, they don't match.  We can't see your package to know what the mapping...

this also looks like a possible execution of DTEXEC from the command line (instead of SSIS catalog/SSIS Execute step from sql agent) - and in this case its likely it...