Another thing that can be affected if there internal fragmentation (large number of VLF's) is replication, I'm not sure whether your db is replicated but just another consideration.

I would say go for it, I looked around for a long time and didn't find much info out...

Sure was

The test log shrank to 3mb.

My aim is to shrink the log files as small as possible so I can manually allocate the initial size. We are seeing high numbers...

Hooray!! That worked!

Did some additional testing there must be something weird going on with...

The file name and info matches in sys.database_files, sys.master_files, sys.sysaltfiles and dbo.sysfiles...

We are in simple...

Yes I can physically see the file there

Running SELECT * FROM test.dbo.sysfiles I got the following

[/code

fileidgroupidsizemaxsizegrowthstatusperfnamefilename

116705152-1020test_dataJ:\SQLdata\test_data.mdf

201280415-164000660test_logH:\SQLLog\test_log.ldf

32823280-16400020test_indexG:\SQLIndex\test_index.mdf

411363672-16400020test_data1P:\SQLData\test_data1.ndf

Name in the first column in 'test_log'

You could use substring to chop the char(101) into 4 char(30) fields in a view.

Code below to create a view named 'SplitInto30Char', splits 'test_field' which is in a table into...

Check the role for the SQL Server Service account, is it set to sysadmin?

Here's a good article on some work around code for this problem.

Other thing to check would be...

Here are some suggestions from around the web, not sure whether they apply as you don't have a whole lot of information to go on.