I changed it to nvarchar(100) and it worked. Now it's possible to create an index to search quickly on
You can limit the field length in the database, for example to nvarchar(40) to be able to store formatted GUID strings. That does not change the way Diafaan SMS Server handles the information in the field. The nvarchar(max) field type is just a suggestion to indicate that Diafaan SMS Server can handle large strings in the MessageGuid field, but this is not a requirement.
I have recently bought and installed a new version of Diafaan. Our previous version was from approx 2012.
We have previously been able to "join" MessageOut and MessageLog by setting a guid into the UserInfo field.
I think MessageGuid now could be used for that. Unfortunately I saw that MessageGuid had the same datatype as UserInfo, ie nvarchar(max) which can't be used in an index.
Can I somehow recreate the tables and use another datatype for MessageGuid or how does it work?
This is not critical as one can use an indexed MessageTo (phone-number) in the join and thereby get a quite good join, but of course the datatype of MessageGuid shouldnt be nvarchar(max), should it?
Kind regards RogerW.
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 616
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1312