In a heap, the data and indexes are processed independently. 

When you are doing any DML on a heap table, you will get I-Os to any index you use, and then a...

Apart from the anti-virus and intruder detection software our security people require, we run nothing else on the SQL Server box.  ...except for backups, integrity checks, etc.  ...and sometimes a...

I recently did an investigation about SP4, which I have summarised below.  In the end we have decided to stick with our SP3 + HF 928 build until next year when we...

1) Windows Task Manager does not properly report usage of memory above the 4GB line.  Your AWE memory usage is not shown in Task Manager.  You can track AWE usage by...

We have had a similar issue on a server that is SAN connected.  However all of our I-O errors were in tempdb which uses the only local disks on the...

I mis-read the original post.  On a 8GB box server 2 would have access to 7GB with AWE enabled.

Note that only the database bufferpools can go into AWE memory.  All...

There are a lot of questions here.  I can only answer some of them.

If all the servers you want to replicate to will be SAN-attached, you should look at SAN...

If all else fails, run

UPDATE msdb..sysjobs SET originating_server = @@SERVERNAME

You can now manage the jobs locally

Server 1 will never use AWE because there is not enough memory on the machine.  SQL will have access to 3GB memory due to the /3GB switch.   It will do...

If I understand you correctly, you want to restore an old copy of master but call it something else, such as FRED.  If you do this there will be no...

If you have access to a 'Crash & Burn' server it is worth trying out some of these tricks. 

Recently I was asked to get SQL working on a server...

The problem of a large IN list is not confined to SQL Server.  If I was doing this work in DB2 or Oracle I would not want to see an...

I was going to suggest the same as Nagabhushanam, but I got there second...  Anyway, the suggestion given is without doubt the best way to go.

BACKUP LOG ... WITH TRUNCATE ONLY is doing what it says on the can.  Run the backup log process but ONLY truncate the log file. 

You need to do a...

This can be fixed.  You need to start SQL with the -T3608 and -f flags, and do the work in Query Analyzer.

1) Start SQL and QA as above

2) Run sp_attach...