I can't find the link to this info but I pasted the entire document.

Hope this helps with the AWE. We went round and round about it.

Memory Use in SQL...

We did not enable AWE on our 64-bit 16 CPU Enterprise 9.0.3186 version using Windows 2003 sp2

we changed a few sp_configure parameters.

I am not sure if because you are using...

Windows Server 2003, Standard Edition supports physical memory up to 4 GB.

We did not enable AWE in any of our 64-bit Enterprise version 9.0.3186 for SQLSvr2005 with 16 CPU but you might need to.

http://msdn.microsoft.com/en-us/library/ms190673.aspx

I hope this article helps

Windows Server...

I just went through a similar scenario

I need a little more info:

@@version

how many CPU?

exec sp_configure

go

Are you clustered?

have you ever run BPA for 2005?

what version of Windows 2003 are you on?

what does the SQLSvr Error Log have posted for this timeframe?

let's get an answer back before we do anything. Need to know information before moving forward.

you never gave us this information

1.

select name, recovery_model_desc, page_verify_option from sys.databases

2. What was...

I would like for you to do the following if it is ok

--run

exec sp_helpdb [name of db you are talking about growing so large]

go

--we need to see how fast your...

what do you get when you run the following commands:

DBCC SQLPERF(logspace)

DBCC LOGINFO