Hi James Toner,

This is not a GroupShare issue. SQL Server should be managed by your Database Administrators.

Please let them know that the operations like 'DBCC SHRINKFILE' need to be executed on your TempDB to affect the TempLog.

More details on TempDB: https://docs.microsoft.com/en-us/sql/relational-databases/databases/tempdb-database?view=sql-server-ver15

We have a statement which may help. Please reach out to your Database Administrators and ask them to research and implement the below into an SQL Job:

USE [tempdb]
GO
DBCC SHRINKFILE (N'templog' , 128, TRUNCATEONLY)
GO
DBCC SHRINKFILE (N'templog' , 128)
GO

This is a general advice and it may not be applicable to your own SQL Server. It may also be possible that the above statement will not have any impact on your TempLog file due to active transactions.

If your SQL Server is dedicated to GroupShare, it may be required that you stop all SDL Services before proceeding.

If your SQL Server is shared with other applications, it may be necessary to stop all connections to the SQL Server before the statement will have any effect.

You may also want to check with your Database Administrators on your backup strategy and adjust your Databases' Recovery Models if required. Further, you may want to check your TempLog Autogrowth setting

I hope this helps.

Radu

Radu Botoiu Hi Radu, thanks for your response.

The DBA is managing the SQL server in line with recommended practice. But the dbtemp file fills up perpetually and exponentially. Currently, it takes an hour to get to 100gb.

This is because there is an "active transaction" reflecting a query from a service called "TV Query" via SDL System, from the application server. We are also noting abnormal logging activity on the application server - i.e., a log that is writing many hundreds of copies a day.

So we do believe that the root problem is with the GroupShare.

Thanks for your input.

Best, James

HI James Toner , did you manage to resolve this issue with "filling transaction logs"?
We are experiencing same issue and it started to show after the upgrade to GS 2020 SR1 CU4.

I see the error in APplicationService.log  saying: 

System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SDL_GS20_TmSystem' is full due to 'LOG_BACKUP'.

HI James Toner , did you manage to resolve this issue with "filling transaction logs"?
We are experiencing same issue and it started to show after the upgrade to GS 2020 SR1 CU4.

I see the error in APplicationService.log  saying: 

System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SDL_GS20_TmSystem' is full due to 'LOG_BACKUP'.