The two queries are different: the first one returns the first row (by created_on) for each group on (c.forex_tag_no ,c.paying_agent_cd).

The second query returns one row based on no order.

Stick to...

You're missing some part of the statement, I'll assume it's just the UPDATE part at the top.

Here's how you do it:

UPDATE t1

SET t1.TotalTest1 = coalesce(t2.SumAmountTest1, 0.00)

,t1.TotalTest2 = coalesce(t2.SumAmountTest2, 0.00)

,t1.TotalTest3...

Cough... BCP 🙂

In windows the line separator is CR+LF. In linux it's LF.

CR = CHAR(13)

LF = CHAR(10)

The synonym points to the remote server and it won't do anything different from using the four-part name (server.database.schema.table) directly. It's exactly the same from a performance standpoint.

SQL Server Data Tools can do that, and it's free. It won't output an Excel file though.

Concat NULL yelds NULL:

SELECT

ISNULL(SAD.HOUSENUMBER + CHAR(13) + CHAR(10),'') +

ISNULL(SAD.ADDRESS1 + CHAR(13) + CHAR(10),'') +

ISNULL(SAD.ADDRESS2 + CHAR(13)...

A very bad design. Talk to him and explain why...

What do you mean? What are you trying to do? Please add more details.

Maintenance plans suck:

1) No appropriate logging

2) Rebuild indexes that are not fragmented enough

3) Rebuild indexes that are too small to benefit from rebuild

I strongly recommend that you stop using maintenance...

Can you please post expected output as well?

BCP in and out one table at a time.

LInked servers are not meant for heavy data transfer. The process would end up being unacceptably slow.

BCP data in and out. You can script the whole thing using sys.tables.

1. If you're about to bulk load data, creating indexes afterwards will speed up the load process. Otherewise, create the indexes upfront.

2. The clustered index IS the table, so it...

Partitioning is not a performance feature and whether it's going to speed up some queries or not heavily depends on how queries are written. If every single query uses the...