Just to clarify, the connection is coming from client machines running on Windows XP 32 bit. The connection should be seamless through ODBC. You cannot use an x64...

They have issues with the dedicated DB server being 64 bit. There is no DLL or .NET framework involved on the server. This is a client application talking...

BTW.... on occasion there is an ambiguous error, at other times the application simply dies on the local workstation. I have done Profiler traces and there is nothing out...

This is a simply client app, conenction via ODBC. TSQL through the ODBC.

I can think of no issues there.

How long has it taken to go from x to 3.8GB?

Are you sure this is expected volume? I would run Profiler to ge a better grasp on what is...

Unlimited growth is fine, the important part is in what increments is it growing, by MB, by %?

The database file is only 580MB?? I would presume it is growing...

Keep in mind too that these autogrowths are hurting server performance. Auto growth should be a last resort.

How large is the database (mdf)?

Well then you need to size the log accordingly. Shrinking it down to the smallest value is only going to result in auto growths.

Keep in mind too that "long...

Is this a highly transactional system?

"And your log file will never grow again"

Not actuallly correct. A log file can absolutely auto grow even when utilizing the SIMPLE recovery model. One "long" running transaction...

Are you backing the log file up on a regular basis?

Ok, to clarify my question......

I am running SQL Server 2000 Enterprise Edition on Windows Server 2003 Enterprise x64. Of coruse, SQL Server is x32 since there is no x64...