sounds like you have the 3gb switch enabled in boot.ini

I'm not sure I totally follow your setup, sorry, you have three nodes, is there one instance on each ?...

the correct memory usage is reported in sysperfinfo.

I sometimes think we go around and around chasing our tails on some of these posts - yes sql standard can only use 2gb of ram ( 32bit sql 2000...

I'm with Jeff  ..views and performance = oxymoron

ok - so I can't see the data but run a plan and if the select within the IN statement is scanning the clustered index or doing a bookmark index...

Richard - sounds like you have parallelism issues, something discussed many times on this site. The most obvious answer to reporting issues is to report from a read only database...

I'm pretty sure you can't do what you're asking as such - however if you create an unattended install script then it might be possible, I only ever used one...

you also need trace flag 1206 and probably 1205 as 1204 only gives part of the story.

I believe these two trace flags are "undocumented"  so usual rules apply.

cool! it's an interesting old world!! Yup I'd say 4gb would be good.

sadly there's no magic answer to this. single column indexes may help but often they are ignored. Basic index would include a primary key, a clustered index ( which may...

you can also create binary checksums and compare the checksums to look for differences. Check BOL.

sadly there are some well documented memory issues with sql server, they can be pretty obscure and if you really want to read through the kb articles that relate to...

The Microsoft SQL Server performance tuning technical reference  sets out the information you need, it's not an answer to every situation but it does cover the reasoning and calculations to...

Using filegroups is an architecture issue and depends upon your circumstances so there is no simple answer that fits all.

Filegroups add an extra level of complexity and can cause performance...

I just had one passing thought, from experience, if you've scheduled the dts to run through a job which runs the job by the guid, then a casual save of...