Update doc (#277)

Delete partition table workaround page
Fix broken PostgreSQL documentation links
Remove COLLATE database_default workaround page
Updated text in FAQ
Updated Client Tools ordering

Signed-off-by: Shard Gupta <shardga@amazon.com>

Author: shardgupta

_client/other-tools.md

@@ -16,14 +16,13 @@ if you face an issue.
 
 The following interfaces are officially supported:
 
+- Open Database Connectivity (ODBC)
 - OLEDB Provider/MSOLEDBSQL
-- OLEDB Driver/SQLOLEDB (deprecated by Microsoft)
-- .NET Data Provider for SQL Server
-- SQL Server Native Client 11.0 (deprecated by Microsoft)
+- Java Database Connectivity (JDBC) version 8.2.2 (mssql-jdbc-8.2.2) and higher
 - Microsoft SqlClient Data Provider for SQL Server
-- Open Database Connectivity (ODBC)
-- Java Database Connectivity (JDBC)
+- .NET Data Provider for SQL Server
+- SQL Server Native Client 11.0 (deprecated)
+- OLEDB Driver/SQLOLEDB (deprecated)
 
 More connectivity drivers might be added in the future.  Since Babelfish supports the TDS 
 protocol, most TDS-based client applications are expected to work with Babelfish.
-

_faq/index.md

@@ -55,7 +55,7 @@ serverproperty
 
 ## Can I use a database with the TDS protocol and the PostgreSQL protocol at the same time?
 
-Yes. A database can support PostgreSQL syntax and SQL Server (TDS protocol) syntax at the same time, but [objects created in one syntax may not be accessible to the other syntax](https://babelfishpg.org/docs/usage/interoperability/).  
+Yes. A database can support PostgreSQL syntax and SQL Server (TDS protocol) syntax at the same time, but please refer to the [Interoperability](https://babelfishpg.org/docs/usage/interoperability/) guidance section.
 
 ### Which TDS clients are known to work with Babelfish?
 

_workaround/collate_database_default.md

@@ -8,16 +8,13 @@ You can use the workarounds in this section to replace unsupported SQL Server sy
 
 | SQL Server feature | PostgreSQL feature | 
 | ------- | ------- | 
-| SQL Server Replication | [PostgreSQL Replication ](https://www.postgresql.org/docs/current/high-availability) |
-| DBCC CLEANTABLE | [PostgreSQL VACCUUM utilities](https://www.postgresql.org/docs/15/routine-vacuuming) |
-| SQL Server full-text search | [PostgreSQL full-text search ](https://www.postgresql.org/docs/15/textsearch) |
-| SQL Profiler | [auto_explain ](https://www.postgresql.org/docs/current/auto-explain) |
-| SQL Server spatial features | [PostGIS spatial data handler](https://postgis.net) |
+| SQL Server Replication | [PostgreSQL Replication ](https://www.postgresql.org/docs/current/high-availability.html) |
+| DBCC CLEANTABLE | [PostgreSQL VACCUUM utilities](https://www.postgresql.org/docs/current/routine-vacuuming.html) |
+| SQL Profiler | [auto_explain ](https://www.postgresql.org/docs/current/auto-explain.html) |
+
 
 
 ## Workaround List
 
-- [COLLATE DATABASE_DEFAULT](https://babelfishpg.org/docs/workaround/collate_database_default)
 - [Dynamically defined cursors](https://babelfishpg.org/docs/workaround/dynamically_defined_cursor)
-- [Partitioning workaround for a cluster running in Single DB mode](https://babelfishpg.org/docs/workaround/partitioned_table)
 - [Rebuilding table indexes](https://babelfishpg.org/docs/workaround/rebuilding_table_indexes)

_workaround/partitioned_table.md

@@ -1,15 +1,6 @@
-[Partitioning]
-doctxt=[Partitioning Workaround](https://babelfishpg.org/docs/workaround/partitioned_table/) - Babelfish code supports PostgreSQL-style partitioning on the PostgreSQL port, but use of PostgreSQL-styled partitioned tables from the TDS port is not recommended.
-
 [SET ROWCOUNT]
 doctxt=[SET ROWCOUNT workaround](https://babelfishpg.org/docs/workaround/set_rowcount/)
 
-[COLLATE]
-rule=collation
-list=DATABASE_DEFAULT
-supported-2.2.0=DATABASE_DEFAULT
-doctxt=[COLLATE DATABASE_DEFAULT workaround](https://babelfishpg.org/docs/workaround/collate_database_default/)
-
 [Parameter value DEFAULT]
 rule=execute_parameter,function_call
 list=procedure,function