If you're transaction log file (TGCMRT.ldf) has that size, there ain't enough room to let SQL handle this cause it needs certainly the same size to fix this. Here's some more info on transaction log files but be aware that this is pure SQL-sided information:

Transaction log principles

Whenever a data update is made entries are added to the transaction log.

It is not possible to prevent this as it is part of the way sql server maintains integrity - particularly during recovery.

The transaction log is a circular file i.e. when the end is reached any free entries at the start will be used.

This means that all being well the file will stay at a constant size as the current entry cycles round.

The system maintains the MinLSN which is a pointer to the first active log record.

Any log records before this (in the circular file) are free.

The MinLSN will be prevented from moving forward by any open transactions - i.e. the oldest open transaction entry will be >= the MinLSN.

The MinLSN is updated at checkpoint so committing a transaction will not immediately free entries and anything that holds up the checkpoint can cause problems.

If the database is in simple recovery mode all entries prior to the MinLSN will be freed at checkpoint.

If the database is in full recovery mode (and a full backup has been taken) the entries prior to the MinLSN will only be freed by a transaction log backup (not full backup).

Unfortunately the sql server default (except local editions) leaves the databases in full recovery mode.

This menas that if no action is taken no tr log entries will be freed and the log file will eventally fill the disk and crash the system.

The SQL Server installation process is very simple and commonly carried out by inexperienced personel. This will appear to work happily but cause problems later.

I would recommend always setting the model database to simple recovery mode to set the default for new databases.

If the log file has grown do to being in full recovery mode then set it to simple before going any further. This should immediately stop the log from growing.

Enterprise manager

Right click on the database, properties, Options, set model to simple, OK.

t-sql

sp_dboption [dbname], 'trunc. log on chkpt.', 'true'

Shrinking the transaction log file (.ldf)

Before this make sure there are free entries by setting the recovery model to simple or backing up the log.

Enterprise manager

Right click on the database, All tasks, Shrink database, Files, Select log file, OK.

t-sql

dbcc shrinkfile ([db_log_name])

Here [db_log_name] is the logical name of the log file as found from sp_helpdb or the table sysfiles

I think this kind of problem can be solved but it might take several days or more.

Safest way is surely trying to make a backup of both mdf & ldf-file first.

You could try the shrink method first. After that, I would try to copy these 2 files to another PC with big enough harddisk (500GB) and the same version of SQL.
Try to attach those 2 files to a SQL server on another machine and see what SQL does with it. Afterwards try to "shrink" the transaction log file and if successfull copy files back to the WinCC PC but before you try something, make sure to have a backup of both files first!

SteBo

Anyway, I would try shrinking the ldf first. It shouldn't become that big but it might fail cause the ldf-size is bigger than the free space on your disk:

Once again, make sure to have a backup first (mdf & ldf).
Open Sql Server Managment Studio, rightclick your database and go to Tasks -> Shrink -> Database

According to some online sources, you can also detach the database, delete or rename the ldf-file, attach the database and a new empty ldf will be created but whatever you try, it will all be tricky and time consuming.

http://www.codeproject.com/KB/database/truncate_log_SQL_server.aspx

Our problem is simply that we know the .ldf lost linkage to the old segmentation, but we just don't know how to make the linkage recovered correctly.

Personally ~ I will sugguest not to do anythink may harm the integrity of the archive segment any more.

Please understand this~ SteBo

Regards,
Komi

New question published by bilalzaidi is split to a separate thread with the subject Two problems with PCS7 WinCC V6.0.

Best regards
Min_Moderator