anchor.diff:  
   I am happy to announce the release of Debezium *1.9.0.Beta1*!
   
  -This release includes many new features for Debezium Sink including Knative event support,
  +This release includes many new features for Debezium Server, including Knative Eventing support and
   offset storage management with the Redis sink,
  -multi-partitioned SQL Server scaling,
  +multi-partitioned scaling for the SQL Server connector,
   and various of bugfixes and improvements.
   Overall, https://issues.redhat.com/issues/?jql=project%20%3D%20DBZ%20AND%20fixVersion%20%3D%201.9.0.Beta1%20ORDER%20BY%20component%20ASC[56 issues] have been fixed for this release.
   
  
positive.code: debezium.sink.http.url=https://<hostname>/<end-point>
  ```
  
  We're super excited about this new sink connector and we look forward to all your feedback!
  
  == Multi-partitioned SQL Server scaling
  
  Some database platforms, such as SQL Server and Oracle, support the creation and management of multiple logical databases within a single database instance.
  Traditionally, streaming changes from the multiple logical databases required a separate connector deployment.
  Now there isn't anything innately wrong with such a deployment strategy, but it can quickly start to show its shortcomings if you have many logical databases and then there is also the concern of one task per connector.
  
  Over the last several 1.x releases, a tremendous amount of work has gone into key fundamental changes to Debezium's common connector framework, setting the stage for a new horizontal scaling strategy.
  
  One of the initial goals of this new strategy is to eliminate the need for multiple connector deployments when streaming changes from multiple logical databases within a single SQL Server instance.
  Additionally, it was critical to expose metrics in a way that enables monitoring tools to report on the state and health of the connector both from a connector-centric perspective but also  from each logical database being processed.
  In this release, we've achieved those goals.
  
  But this is just the beginning folks!
  
negative.code: This is not an exhaustive list nor has this list been prioritized and scoped to what you can expect in totality of 2.0;
  however,
  it is what we've identified to be things that either the community or the team feel are actionable tasks for this new major release.
  If there is something you would like to see, please take a moment and either raise a discussion on the above Jira ticket or join the discussion on https://groups.google.com/u/1/g/debezium/c/X17AUmQ88-E[this topic] on our mailing list.
  