IMO the question tended to "would it hurt to always activate AWE" .... That answer is "Yes".

Don't enable it, if it is not needed.

- You shouldn't have switched them to simple recovery, before you have the answer to your question.

If you hadn't switched it to simple recovery, you might have been able to...

Yes it is !

But if you need to address more than 8GB RAM on a 32-bit system, it is the only option.

from books online (BOL) SQL2008

SQL Server supports Address Windowing...

You could enable C2 auditing and process the trace file to persist the data you want to.

(have a look at BOL for its content)

Maybe even my little article "SQL...

raym85 (9/20/2009)

---

Would putting the queries in a Sproc be faster? I thought both functions and sprocs parsed and pre-compiled the data. Meaning that performance would be better? Well maybe not...

or use the ever lasting exists with a correlated subquery.

SELECT Q.*

FROM qtral Q

WHERE exists (SELECT 1

FROM qtral Qx

where Qx.tral_no = Q.tral_no

and Qx.tral_pd = Q.tral_pd

group by Qx.tral_no, Qx.tral_pd

having...

The big problem with functions that perform queries, is that they cause hidden joins, hence should be transformed to (well tunable) regular joins !

Functions aren't always visible at first sight...

have a look at Allens article : http://www.simple-talk.com/sql/backup-and-recovery/alert-based-transaction-log-backups---automate-your-database-maintenance-part-2/

afaik size doesn't matter, unless you have a sqlexpress instance.

There has been a limit regarding the number of files when using sp_attachdb.

Best is to use "create database .... for...

There are only two reasons why one should stop and restart a sqlserver instance:

- to apply a servicepack/hotfix

- to have tempdb to its original or set starting size ( in...

- commit and overwrite .. yes , SHRINK ... No !

- things that can cause your log files to grow with simple recovery :

-- long running transactions

-- huge...

Gail posted a very explanatory article on this subject !

http://www.sqlservercentral.com/articles/64582/

start with the Upgrade advisor for sql2005 !

It will point you to potential issues with your db.

- if a filegroup gets filled up and cannot auto extend any files , you'll get an errormessages stating "filegroup full".

So you nolonger can add data to it, rebuild indexes,...

- also, with these ndf files, it is best to know if they are all allocated to a single filegroup or not. Having multiple files allocated to a filegroup would...