I’m being told by epicare these are the only tables they allow turning on CDC?
This is obviuosly wrong. Collaborate Notifications cannot event work with out this.
WTF is going on over there?
I didn’t think Collab was available for SaaS customers.
its on our invoice and it once worked in pilot - trying to get it up on live.
Yeah I don’t see how that can be correct - enterprise search and spreadsheet server both require cdc for a lot more tables than that and both of those are available in the cloud.
It is. We have it.
When was the last time that worked?
Its been working since they re-enabled it for cloud last year . . .
Not on mine.
Maybe you didn’t ask?
I didn’t. How ridiculous is it that I would have to?

i asked nicely and you see where that got me. someone call @pferrington ![]()
I think it’s a SaaS product itself, isn’t it? Even for on-prem people. But I could be full of search.
It is. And fun fact, if (when) it goes down, it crashes your on prem users sessions. So that’s fun…
Just so you all know, I am aware of this and working with cloud operations. I make no promises or forward looking statements ![]()
What I can say is it is a historical concern about two things:
customers turning on table tracking but not scheduling the CDC Processes can result in extreme bloat in the CDC.CaptureLogTable
Although most do not notice or don’t care, CDC tracking is handled by DB triggers and there is a performance cost for enabling it. I don’t have exact numbers because it will very but it can add as much as 5-7% to CrUD operation (no cost for read of course).
Sir, your reply is greatly appreciated. Have a great weekend!