Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's simply no advantage of using MERGE in this situation. Why overcomplicate? Stick to the KISS principle, for chrissake.</p> <p>Anyways, here's the script:</p> <pre><code>declare @targetTableName varchar(100) = 'target' ,@targetSchemaName varchar(20) = 'dbo' ,@sourceTableName varchar(100) = 'source' ,@sourceSchemaName varchar(20) = 'dbo2' ,@matchCondition varchar(50) = 't.id = s.id' ,@columns varchar(max) set @columns = (select ','+quotename(c.name) from sys.tables t join sys.columns as c on t.object_id = c.object_id join sys.schemas s on s.schema_id = t.schema_id where t.name = @targetTableName and s.name = isnull(@targetSchemaName, s.name) for xml path('')) --a column name starts with a comma declare @sql varchar(max) = ' merge @target t using @source s on @matchCondition when not matched then insert (@columns) values @sourceColumns' set @sql = replace(replace(replace(replace(replace(@sql , '@matchCondition', @matchCondition) --replace @columns with column list with the first comma removed , '@columns', stuff(@columns, 1, 1, '')) --replace @sourceColumns with column list with the 's.' prefix and comma removed , '@sourceColumns', stuff(replace(@columns, ',', ',s.'),1,1,'')) , '@target', quotename(@targetSchemaName)+'.'+quotename(@targetTableName)) , '@source', quotename(@sourceSchemaName)+'.'+quotename(@sourceTableName)) print @sql --exec(@sql) </code></pre> <p>And we'll get something like this:</p> <pre><code>merge [dbo].[target] t using [dbo2].[source] s on t.id = s.id when not matched then insert ([column1], [column2], [column3], [column4]) values s.[column1], s.[column2], s.[column3], s.[column4] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POMERGE Command in SQL Server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDenis Valeev
    1. USDenis Valeev
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODenis- Nope, I found it a lot more optimized way. I had a 5 lakh+ rows in my source table which caused the 1st query to run for about 45-50 minutes. The change to MERGE command made it complete in seconds :-D :-D So I definitely need a change.
      singulars
      1. PO
      1. UStamizhan
    2. COThis just doesn't make any sense. MERGE reduced to simple INSERT cannot perform better or worse than the latter. I can't just wrap my head around of what you just said. :D
      singulars
      1. PO
      1. USDenis Valeev
    3. COAs to the long-running query, did you try to specify "with(nolock)" on the source table? And believe me, MERGE just can't perform THAT better.
      singulars
      1. PO
      1. USDenis Valeev
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload