HI,
We are looking into customizing this procedure to avoid merging of records are not duplicates. Can somebody shed some light on where this procedure is placed (called within another procedure or something) within Tessitura. This will give us understanding of effects of this procedure run. Thanks for your time and help.
Cheers
Harpreet
We have had a customized LP_Validate_Cust_Merge for quite some time now.
However, with V12.1 we have started to get an error message every time the RaiseError is called.
On the client side it looks like this.
Invalid Entry
Merge not permitted by LP_VALIDATE_CUST_MERGE.
Warning: Null value is eliminated by an aggregate of other SET operation.
Anyone else run into this?
Anyone else have a quick solution?
Here is the type of code that is throwing the error.
if ( not (@Ug_contest like 'PlanM%' and @Ug_contest <> 'PlanMgr') and @delete_id_count > 0)
Begin
RAISERROR ('Merge not possible: Only Membership can merge %s', 16,1,@msg1)
RETURN
End
Unknown said: Merge not permitted by LP_VALIDATE_CUST_MERGE.
By default LP_VALIDATE_CUST_MERGE and LP_CONST_MERGE have old raiseerror syntax that we found that SQL 2012 doesn't like. In both sprocs I had to look for syntax like, e.g.
Begin RAISERROR 50000 'Merge not possible: Delete ID is an Opera Subscriber and Keep ID is not! Try reversing the selection.') RETURN End
And replace it with something like
RAISERROR (N'Merge not possible: Delete ID is an Opera Subscriber and Keep ID is not!
Try reversing the selection.', -1, -1)
Does anyone have a working LP_VALIDATE_CUST_MERGE that works with SQL Server 2016 at Tessitura 12.5.1 that they would be willing to share?
I don't have a solution to this, but now I'm worried. Do we have a list of everything that breaks when we move from SQL 2008R2 to SQL 2016?
David Vivino (Past Member) said:Do we have a list of everything that breaks when we move from SQL 2008R2 to SQL 2016?
Other than the "raiserror" stuff above, not aware of anything in the standard code breaking due to move from 08R2 to later versions.
Hi David - back when we upgraded from 2008 R2 to 2012, we ran into the "raiseerror" issue described in this thread. We upgraded to SQL Server 2016 SP1 from 2012 in our 14.1.2 test environment, and so far have had no issues. We aren't live yet - but our experience so far mirrors what Chris said.
We have been testing a change 2008R2 to 2016 as part of a move to RAMP.
Another thing that we found is that some SSRS reports were working OK on onsite even if you don't have IMP USERS on the stored procedure. When we got to RAMP on 2016 these reports stopped working. This may not be part of the 2016 change.
Hi Chris (and Gawain Lavers and )
This fix was very helpful. We thought we'd broken something else in 14.1.
What does the N do in "RAISERROR (N'Merge not possible..." ?
Michael Longfield said:What does the N do in "RAISERROR (N'Merge not possible..." ?
"You may have seen Transact-SQL code that passes strings around using an N prefix. This denotes that the subsequent string is in Unicode (the N actually stands for National language character set). Which means that you are passing an NCHAR, NVARCHAR or NTEXT value, as opposed to CHAR, VARCHAR or TEXT."
From:
stackoverflow.com/.../what-is-the-meaning-of-the-prefix-n-in-t-sql-statements
It casts the string as an NVARCHAR.
Don't know if I ever sent you this:
https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_technical-9/19096/polling-v14-sql-server-2014-upgrade-experiences
My experience was that there wasn't a lot. The primary issue I had revolved around changes to our RAMP environment, not SQL Server itself.