Skip to main content

I'm facing an issue with selecting schemas to observe for schema change detection in Observability for one of our sources(Sybase).

Context:

In our SQL database source setup, we have a single connection that includes multiple schemas, and Observability allows us to select multiple schemas without issue, as shown below.

However, for the Sybase source, we're unable to select multiple schemas under a single connection. I only get the option to choose one connection and one schema from the dropdown. (See screenshot below.)

Ideally, I’d like to select all dbo across all connections to monitor for structural changes.

Question:

Has anyone experienced a similar limitation?
Is there a recommended approach for configuring Observability for schema checks on sources that have multiple connections and schemas under a single source — especially in cases like a Sybase database, where multiple connections are used?

Any guidance or best practices would be greatly appreciated.

Hi ​@Gerson, you should be able to select multiple schemas when configuring data observability on a source with multiple connections. There shouldn’t be any difference between technologies in that regard -- but to select multiple schemas you first need to pick a connection. There isn’t a way to browse all schemas across all connections in one screen.

Is it possible that the dropdown on your screenshot is the list of connections, not schemas? Once you select one of the connections, can you pick some schemas, then select another connection and pick more schemas there? 

Hi Lisa, 

Yes, you're right the first dropdown at the top is the list of connections within the source, and dbo is the schema associated with each connection. When I select a connection and choose a schema, I expect the selected schema to appear at the top, and I should be able to repeat this process for multiple connections, with each selected schema being listed.

However, in my case, even after selecting schemas from different connections and saving, only the schema from one connection is actually saved. The schemas from the other connections are not retained.

Hi ​@Gerson I can’t seem to reproduce what you’re describing - would you mind opening a ticket on our support portal? A screencast showing your process step by step would be awesome. Thank you in advance! 

Reply


Community Terms of Use & ConditionsCookie settings