Ben,
Thank you for the reply.
I have done a Full backup and a log backup. And the log file is still the same size.
So to look at the log space size and allocation I used the DBCC SQLPERF(LOGSPACE); function which returned values of:
databaseName 531103.6 1.064952 0
Which tells me that the log file has been truncated.
So I tried the shrink operation noted in the technote
http://seer.entsupport.symantec.com/docs/253528.htm and the log file was still the same size.
The technote above had a link to another technote so I went there and it described a manual shrink process called SHRINKFILE, which I tried with the same results.
So I looked up DBCC SHRINKFILE (Transact-SQL) on MSDN and found that I should now do the following put the db into simple recovery mode, shrink the file then put it back into FULL recovery mode
_________________________________________________
GO
-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE DatabaseName
SET RECOVERY SIMPLE;
GO
-- Shrink the truncated log file to 100 MB.
DBCC SHRINKFILE (DatabaseName_log, 100);
GO
-- Reset the database recovery model.
ALTER DATABASE DatabaseName
SET RECOVERY FULL;
GO
_________________________________________________
So I tried this on our developement server and it worked fine.
What I would like to know is do you suggest this. And if so should I create a job to do this each week after a full backup and a log backup.
My plan for backup is this. Full backup on Sunday night, log backup M-F and then a ShrinkFile on Saturday after the Log backup.
Thanks again.