Merge pull request #4327 from segmentio/DOC-521-IG

Remove Compose docs [DOC-521]

Author: forstisabella

src/connections/storage/catalog/postgres/index.md

@@ -15,10 +15,8 @@ PostgreSQL is ACID-compliant and transactional. PostgreSQL has updatable views a
 Segment supports the following Postgres database providers:
 - [Heroku](#heroku-postgres)
 - [RDS](#rds-postgres)
-- [Compose](#compose-postgres)*
 
-> note "Deprecation of Compose"
-> On March 1, 2023, [Compose will be deprecated](https://help.compose.com/docs/compose-deprecation){:target="_blank"}. After this date, all databases on Compose will be disabled and deprovisioned. If you need help selecting another Segment-supported Postgres database provider, [contact Segment Support](https://segment.com/help/contact){:target="_blank"}.
+Segment supported a third Postgres provider, Compose, until Compose was [was deprecated on March 1, 2023](https://help.compose.com/docs/compose-deprecation){:target="_blank"}. To continue sending your Segment data to a Postgres destination, consider using either [Heroku Postgres](#heroku-postgres) or [Amazon's Relational Database Service](#rds-postgres).
 
 > warning ""
 > Segment only supports these Postgres databases. Postgres databases from other providers aren't guaranteed to work. For questions or concerns about Segment-supported Postgres providers, [contact Segment Support](https://segment.com/help/contact){:target="_blank"}.
@@ -87,136 +85,11 @@ To create a new inbound rule:
 
 8. Click **Save rules**.
 
-## Compose Postgres
-
-> warning "Deprecation of Compose"
-> [Compose will be deprecated](https://help.compose.com/docs/compose-deprecation){:target="_blank"} on March 1, 2023. After this date, all databases on Compose will be disabled and deprovisioned. To continue sending your Segment data to a Postgres destination, consider using either [Heroku Postgres](#heroku-postgres) or [Amazon's Relational Database Service](#rds-postgres).
-
-Compose is the first DBaaS (Database as a Service) of its kind, geared at helping developers spend more time building their applications rather than wrestling with database provisioning and maintenance. Compose provides easy to deploy and scale data stores and services in many flavors: PostgreSQL, MongoDB, RethinkDB, Elasticsearch, Redis, etcd, and RabbitMQ.
-
-Using Compose, companies can deploy databases instantly with backups, monitoring, performance tuning, and a full-suite of management tools. Compose Enterprise brings all this to the corporate VPC (virtual private cloud).
-
-Compose uses Segment for hooking together web analytics, email, and social tracking and manages its Segment warehouse on PostgreSQL. Compose is pleased to be able to harness the power of Postgres to query Segment data and be able create custom reports.
-
-1. set up PostgreSQL
-
-    If you don't yet have an account with Compose, [sign-up](https://www.compose.com/signup){:target="_blank"} and select the PostgreSQL database to get started.
-
-    For those of you already on Compose, if don't yet have a PostgreSQL instance, you can add one from the Deployments page in the management console by clicking "Create Deployment" then selecting PostgreSQL or just [add a PostgreSQL deployment](https://help.compose.com/docs/postgresql-on-compose){:target="_blank"} to your account.
-
-    ![](images/compose1.png)
-
-    Once your PostgreSQL deployment is spun up, you may want to [create a user](https://www.compose.io/articles/compose-postgresql-making-users-and-more/){:target="_blank"} to be the owner of the database you'll use for Segment. There is already an admin user role that is generated on initialization of your deployment, but this user has full privileges for your deployment so you may want to create additional users with more specific privileges. You may also want to manually scale up your deployment for the initial load of Segment data since it loads the past two months of data by default. You can then scale it back down according to your data needs after the initial load. The easy-to-use management console lets you perform these tasks, monitor your deployments, configure security settings, manage backups, and more.
-
-    Now, all you need to do is create a database where your Segment data will live. You can create a database directly from the Data Browser interface in the Compose management console, by using a tool such as the [pgAdmin GUI](http://www.pgadmin.org/download/){:target="_blank"} or programmatically using code you've written. For simplicity, this database is simply named "segment" and associated it to the "compose" user as the owner. Here is the SQL statement to create the database for Segment data, using the default PostgreSQL arguments (set yours appropriately to your requirements):
-
-    ```sql
-    CREATE DATABASE segment
-    WITH OWNER = compose
-    ENCODING = 'SQL_ASCII'
-    TABLESPACE = pg_default
-    LC_COLLATE = 'C'
-    LC_CTYPE = 'C'
-    CONNECTION LIMIT = -1;
-    ```
-
-    And that's it! You don't even need to create any tables - Segment will handle that for you.
-
-2. Browse & Query
-
-    And now the fun part - browsing and querying the data!
-
-    You'll notice in your PostgreSQL database that a new schema has been created for each source that was synced. Under the production source schema a whole bunch of tables were created. You can see the tables in the Compose data browser "Tables" view:
-
-    ![](images/compose1.png)
-
-    When the Segment data is loaded to the PostgreSQL database, several tables are created by default: `aliases`, `groups`, `identifies`, `pages`, `screens` and `tracks`. You might also have `accounts` and `users` tables if you use unique calls for groups and for identifies. To learn more about these default tables and their fields, see the [Segment schema documentation](/docs/connections/storage/warehouses/schema/).
-
-    All of the other tables will be event-specific, according to the event names and properties you use in your `track` calls. The number of tables will depend on the number of unique events you're tracking. For example, at Compose, there is a track call for when customers view their deployments such as:
-
-    ```js
-    analytics.track('deployments_show', {
-    deployment_name: 'heroic-rabbitmq-62',
-    deployment_type: 'RabbitMQ'
-    });
-    ```
-
-    In the Postgres Segment database, there will then be a table named "deployments_show" which can be queried for that deployment to see how many times it was viewed:
-
-    ```sql
-    SELECT COUNT(id)
-    -- Don't forget the schema: FROM <source>.<table>
-    FROM production.deployments_show
-    WHERE deployment_name = 'heroic-rabbitmq-62';
-    ```
-
-    The result is 18 times in the past two months by a particular database user. To verify, just join to the identifies table, which contains user data, through the `user_id` foreign key:
-
-    ```sql
-    SELECT DISTINCT i.name
-    FROM production.identifies i
-    JOIN production.deployments_show ds ON ds.user_id = i.user_id
-    WHERE ds.deployment_name = 'heroic-rabbitmq-62';
-    ```
-
-    A more interesting query for this, however, might be to see how many deployments were created in November using the "deployments_new" event:
-
-    ```sql
-    SELECT COUNT(DISTINCT id)
-    FROM production.deployments_new
-    WHERE original_timestamp &gt;= '2015-11-01'
-    AND original_timestamp &lt; '2015-12-01';
-    ```
-
-    This way, you can create custom reports for analysis on the tracking data, using SQL as simple or as complex as needed, to gain insights which Segment-integrated tracking tools may not be able to easily find.
-
-
-### Database set up - Service user and permissions
-
-Once you have your Postgres database running, you should do a few more things before connecting the database to Segment.
-
-Your database probably has an `admin` username and password. While you _could_ give these credentials directly to Segment, for security purposes you should instead create a separate "service" user. Do this for any other third-parties who connect with your database. This helps isolate access, and makes it easier to audit which accounts have done what.
-
-To use the SQL commands here, [connect to your database using a command line tool](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.IAMDBAuth.Connecting.AWSCLI.PostgreSQL.html){:target="_blank"} such AWSCLI or psql Client.
-
-```sql
--- this command creates a user named "segment" that Segment will use when connecting to your Redshift cluster.
-CREATE USER segment WITH PASSWORD '<enter password here>';
-
--- allows the "segment" user to create new schemas and temporary tables on the specified database.
-GRANT CREATE, TEMPORARY ON DATABASE <enter database name here> TO segment;
-```
-
-### Connect with Segment
-
-1. Open up Segment in another browser window or tab
-
-    Visit the [Segment Workspaces screen](http://segment.com/workspaces){:target="_blank"}. Click the workspace you'd like the database to be associated with.
-
-
-2. Click **Add Destination**.
-
-    In the Workspace, you can find the button beside the Destinations.
-
-
-3. Either select "Warehouses" categories from the left-hand sidebar, or use the search field and look for "Postgres".
-
-
-4. Configure the Database Connection.
-
-    Select Postgres database.  Then, copy the relevant settings into the text fields on this page and clicking **Connect**.
-
-    ![](images/segment4.png)
-
-5. Verify that the database connected successfully.
-
-    You should see a message indicating that the connection was successful. If not, check that you entered the settings correctly. If it still isn't working, feel free to [contact Segment support](https://segment.com/help/contact/){:target="_blank"}.
-
-### Sync schedule
+## Sync schedule
 
 {% include content/warehouse-sync-sched.md %}
 
-![](/docs/connections/destinations/catalog/images/syncsched.png)
+![A screenshot of the sync schedule page. The enable sync schedule is toggled on, and the sync schedule dropdowns are visible.](/docs/connections/destinations/catalog/images/syncsched.png)
 
 
 ## Security
@@ -260,7 +133,7 @@ For more information on single vs double follow [this link](http://blog.lerner.c
 
 ### Can I add an index to my tables?
 
-Yes! You can add indexes to your tables without blocking Segment syncs. However, Segment recommends limiting the number of indexes you have. Postgres's native behavior requires that indexes update as more data is loaded, and this can slow down your Segment syncs.
+Yes, you can add indexes to your tables without blocking Segment syncs. However, Segment recommends limiting the number of indexes you have. Postgres's native behavior requires that indexes update as more data is loaded, and this can slow down your Segment syncs.
 
 ## Troubleshooting