Viewing 15 posts - 16 through 30 (of 38 total)
Thanks! That's what I was missing. Although I can't right now think of an example where I'd want Xact_abort set to OFF.
I am really struggling with implementing error handling...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 27, 2009 at 12:35 pm
Thanks much, I'll proceed along with Try--Catch instead.
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 23, 2009 at 3:43 pm
Can you elaborate on which kinds of errors I would expect to be able to trap using @@error, and which ones I wouldn't? That is, what's the exact definition...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 23, 2009 at 2:55 pm
Thanks for all of your help. The problem was (as Lamprey13 suggested) duplicate PK's in my incoming data.
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 23, 2009 at 1:54 pm
Ugh, even with the sub-query solution, it still isn't working as expected. I'm trying this, as suggested (greatly simplified from the full sql)
To debug, I've commented out the INSERT part...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 20, 2009 at 6:28 pm
Yeah, I've been dealing with this for 20 years, and I long ago gave up beating my head against the wall. This is why I have developed the system that...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 20, 2009 at 11:22 am
SHort answer: Lamprey13, I've gone with your subquery solution.
Longer answer:
ksullivan, don't want to delete the PK constraint.
Grant, I can't use the TOP 1 option because the issue is...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 20, 2009 at 10:03 am
In the infamous words of Rosanne Rosannadanna, "Never mind...."
The problem was simply that primary key Panels$ID and unique index "Panels$primarykey" are indeed two separate entities, and the 2nd one was...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
July 13, 2009 at 3:02 pm
Primary key is there, that's not the issue. I know how to fix it. I'm just curious as to why it's happening, because as Grant said "Although I thought that...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
June 29, 2009 at 12:33 pm
Here is the reply I got from my IT department:
"SQL 2005 x64 does not support the Jet driver needed to make the link server connection you are requesting. Therefore...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
June 25, 2009 at 1:05 pm
At last I have figured it out!
I changed from:
exec sp_executesql @strSQL, @strParTable
To:
exec sp_executesql @strSQL
So my take on this is that I can only pass where-clause-type variables as parameters...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
June 10, 2009 at 5:46 pm
I copied your code into my db and did nothing but uncomment the exec statement. (Oh, and add a missing ")" at the end after par2parunique1.noun).
I get the same error...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
June 10, 2009 at 4:51 pm
Changed code per below. No difference. Still getting the same error, "incorrect syntax near 'PAR1'.
If I understand sp_executeSQL correctly (and there's certainly some doubt of that!), the order in which...
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
June 10, 2009 at 3:46 pm
Could you please illustrate what you mean? (by marking up my code....?)
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
June 10, 2009 at 3:01 pm
Thanks again, I've added that to my request.
[font="Comic Sans MS"]She Through Whom All Data Flows[/font]
May 29, 2009 at 10:11 am
Viewing 15 posts - 16 through 30 (of 38 total)