Viewing 7 posts - 1 through 8 (of 8 total)
I worked out what causes the exception here it is- the statement in the stored proc:
------------------------------------------
insert #SIZES_WORK
(
ProfileItemTypeCode,
MinMaxCode,
PreferenceConversionID,
ProfileItemTypeGroupID
)
select pit.ProfileItemTypeCode,
nm_2,
...
April 1, 2008 at 6:07 am
I've run the upgrade advisor and it didn't mention anything about this proc or the user defined types.
As for the string constant it's a part of the query string...
March 31, 2008 at 8:27 pm
I've run the upgrade advisor and it didn't mention anything about this proc or the user defined types.
As for the string constant it's a part of the query string...
March 31, 2008 at 8:26 pm
Hi Adam
Thanks for the replay. Do you think there could be some permissions or other settings that I need to apply to the master database for example, that would sort...
March 31, 2008 at 6:57 pm
Thanks Karl
will give it a go.
Regards
Raf
March 31, 2008 at 4:12 am
Hi Karl
It's not a collation issue. Have ensured all databases use same collation.
Thanks for the suggestion though.
Raf
March 31, 2008 at 2:58 am
Hi Karl
Thanks for your response. I think the problem is related to conversion issue when comparing values in columns in two tables one being a tmp table. Tried debugging the...
March 31, 2008 at 1:36 am
Viewing 7 posts - 1 through 8 (of 8 total)