Viewing 15 posts - 421 through 435 (of 642 total)
thanks for that. I needed a term. bingo!! 🙂
August 14, 2011 at 4:25 pm
correction, using the WHEN NOT MATCHED THEN INSERT portion of the MERGE statement, I want to insert values into the identity column.
August 8, 2011 at 2:30 pm
I quote Dave Pinal: "One of the most important advantages of MERGE statement is that the entire data are read and processed only once. In earlier versions, three different statements...
August 8, 2011 at 2:08 pm
I have found this forum to be a big part of my morale support and I agree. Prominent members of the SQL DBA/Dev community are here, helping completely anonymous beginners...
August 5, 2011 at 5:49 pm
Well, as I said, those tables are just quick mock ups to illustrate my issue, and do not reflect the naming convention or design practices of the development team where...
August 5, 2011 at 12:37 pm
OK, thank you.
I found the problem. I had an the order of column names in the insert statment incorrectly aligned with the values I was inserting.
Yes, on varchar columns.
Thank...
August 4, 2011 at 12:21 pm
Ok, found that in my INSERT statements I had the column names and values mismatched (wrong order) corrected order to align and am on to bigger better errors.
August 4, 2011 at 11:03 am
Really stumped. Trying to think of what other tests I could use to troubleshoot.
Datatypes and sizes of straight accross data migration are compatible.
In the case of CASE statements, there are...
August 4, 2011 at 10:42 am
OK, please excuse the fact the the problem I am hvig with 'real' merge statement is now different.
When I run the real statement I get the below error:
Msg 8152, Level...
August 4, 2011 at 7:20 am
Thank you. It did populate, didn't it?! :doze:
I will now try with the none-pseudocode.
August 4, 2011 at 7:06 am
OK, Ninja, understood about edit.
Todd, I was going to use that SELECT statement within a CASE statement (inside USING clause).
I was foolish with my question, however, because...
August 3, 2011 at 11:51 am
the answer is, to make the column = NULL (within the select statement). This will populate the column with null values.
Simple as that.
August 3, 2011 at 10:39 am
I found problem. I needed to include the variable in both places where the 'not matched' and 'matched' conditions are specified.
EG:
create procedure testsp_get_fYear
(
@year smallint
)
as
merge new as T
using old as...
August 1, 2011 at 11:01 am
thanks. yes, the first link to msft is the one I was referring to. Thanks for Pinal's, I'll take a look.
July 23, 2011 at 8:20 am
thank you.
Your solution is similar to one I tried to follow here: I have used this and found duplicates. however, there are so many, I don't know how...
July 23, 2011 at 1:42 am
Viewing 15 posts - 421 through 435 (of 642 total)