[cisco-voip] Persistent Chat

[Anthony Holloway]

Oh I see.  Well, since Cisco does mention the following:

"We recommend that you maintain the external database according to the best
practice guidelines described in the product documentation. If you do not
properly maintain the external database, and you allow the external
database to fill up, this causes performance problems in the IM and
Presence Service cluster."

It stands to reason that you could just use the method you described
initially, which is to have your SQL admin write the procedure to delete
records older than X days.

Good luck, and I'd be curious to know which route you take.

On Tue, Feb 12, 2019 at 8:56 AM Erick Wellnitz <ewellnitzvoip at gmail.com>
wrote:

> That works for what loads in Jabber  but they're concerned with the
> messages existing in the database which makes them fair game for legal
> discovery.
>
> On Mon, Feb 11, 2019 at 7:59 PM Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
>> Is it not just the setting labeled  Maximum number of messages that can
>> be retrieved from the archive?
>>
>> On Mon, Feb 11, 2019 at 11:12 AM Erick Wellnitz <ewellnitzvoip at gmail.com>
>> wrote:
>>
>>> All,
>>>
>>> With the introduction of WebEx Teams the request for persistent chat
>>> isn't so common anymore.
>>>
>>> I have a client asking about it and how we can limit how long messages
>>> are kept in persistent chat.
>>>
>>> I can't find a native way to do that but was thinking if IM&Presence
>>> doesn't index the database independently an SQL admin could write a
>>> procedure to remove entries older than x days.
>>>
>>> Any thoughts?
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190212/fe2858ac/attachment.html>