Rather, provide the permission to the SQL Server Service, Service Account i.e. the Windows Account...

As you are using a 32bit version of SQL Server on a 64 bit operating system, you need to enable AWE in order to use memory above 4GB.

You also need...

You're welcome. Glad to help.

Hi,

You should be able to find what you are looking for here:

http://www.mssqltips.com/tip.asp?tip=1158

In addition to what Krishna said,...

Hi,

Take a look at the Microsoft white paper SQL Server 2005 Failover Clustering

I would also suggest that you try and implement a clustered configuration. You can do this on a...

Here are some excellent resource for the tempdb database.

All About the tempdb Database[/url]

Hi,

So you are currently running.

1. Windows Server 64 bit?

2. SQL Server 2005 Standard Edition(32 bit)?

What Edition of Windows Server are you running Enterprise/Standard?

Cheers,

No...

SA (4/3/2009)

---

It's clearly not using AWE. The only thing that's not setup correctly is the fact that the run_value output from sp_configure 'AWE Enabled' is 0 while the config_value is...

EdVassie (4/3/2009)

---

Try asking for less memory when you start SQL Server. If you ask for more AWE memory than what is available to don't get any of it.

Also make...

SA (4/3/2009)

---

Just to re-iterate, the SQL Server box was bounced after PAE and AWE was enabled. Even though the OS now recognizes the 8GB memory, Total Server Memory for the...

Afternoon,

I believe some of the more recent posts, although naturally only trying to assist, are instead confusing the issue somewhat.

To my understanding the original problem was AWE had not been...

Hi,

Can you please re-explain exactly what your issue is?

Cheers,

The /3GB switch is not the answer to your problems. It would however permit SQL Server to have access to an additional 1GB of memory should you wish.

By enabling the...