(Please take this with a grain of salt — I have virtually no experience with MS SQL ... I'm just replying in the hope that any suggestion might be better than none :)
...my stored procedure decides if a record gets inserted or not.
How is tableX related to priceHistory, i.e. how does the result of the SELECT change, once a record has been inserted into priceHistory? In other words, how does tableX help to distinguish if inserting a certain record would produce a duplicate?
Anyhow, sometimes, mysterious DB behaviour is the result of commits not happening when you think they should... I have no clear idea, though, how that would account for the difference between your local and the server machine, but maybe some different AutoCommit default setting of the ODBC driver, or some such. In the absence of any better ideas, I'd try to commit myself, or explicitly enable AutoCommit. Just a thought.
In reply to Re: DBI Inserting Duplicate Records
by almut
in thread DBI Inserting Duplicate Records
by PerlAcolyte
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |