Update troubleshoot-a-full-transaction-log-sql-server-error-9002.md

removing as it's redirecting back to this article
[KB support article - A transaction log grows unexpectedly or becomes full in SQL Server](https://support.microsoft.com/kb/317375)

https://github.com/MicrosoftDocs/sql-docs.fr-fr/issues/125

Author: MashaMSFT

docs/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002.md

@@ -106,7 +106,6 @@ This statement lets you identify the user ID of the owner of the transaction, so
 Sometimes you just have to end the process; you may have to use the [KILL](../../t-sql/language-elements/kill-transact-sql.md) statement. Please use this statement very carefully,  especially when critical processes are running that you don't want to kill. For more information, see [KILL (Transact-SQL)](../../t-sql/language-elements/kill-transact-sql.md)
 
 ## See also  
-[KB support article - A transaction log grows unexpectedly or becomes full in SQL Server](https://support.microsoft.com/kb/317375)
  [ALTER DATABASE (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql.md)   
  [Manage the Size of the Transaction Log File](../../relational-databases/logs/manage-the-size-of-the-transaction-log-file.md)   
  [Transaction Log Backups (SQL Server)](../../relational-databases/backup-restore/transaction-log-backups-sql-server.md)