jlp3630 (8/27/2008)

I'm running RAID-0 on my c: drive (contains Windows, SQL server, master, model and msdb databases and log files).

I'm running RAID-50 on my f: drive (tempdb, user databases and...

SQL does not have a mind of its own. It will not change a database's recovery model unless someone issues a command to do so.

Check any jobs that run...

Then it is databaseID : FileID : PageID

I've seen one before, I can't...

For this kind of error, you should probably contact Microsoft's customer support people. We don't have the tools to read stack dumps and figure out what caused them.

Generally, it's...

What's in the waitresource column depends on the wait type. I'm going to guess that the wait is for a page latch/page io latch and that this resource is databaseID:FileID:...

There shouldn't really be any performance impact.

The main problems you're going to encounter is that you won't be able to use foreign keys (as they require a unique or...

Something within the loop (or someone else) must have changed the recovery model. SQL won't change recovery models on its own

Look for ALTER DATABASE statements within the code you're running....

Can you save the exec plan as a .sqlplan file, zip it and attach it? That will help a bit.

Otherwise, you can check and see if the indexes are being...

To expand a bit, they are orphaned distributed transactions. What happens is that some app uses DTC in it's communications with SQL and then doesn't properly commit or rollback the...

Standard edition ignores the locked pages setting. I would suggest, as...

What error do you get from attaching? If you can't attach the DB, then you're only real option is to restore the backup you have and live with the data...

Strange. Did you run it in database 6?

Have you dropped/truncated any tables since the deadlock message? It could account for why the partition is no longer there.

On 64 bit systems you should limit the max memory. SQL's quite capable of taking all tha available memory and starving the OS. Try setting it to 6.5GB. Dunno if...

SQL 2000 or SQL 2005? The checkDB output looks like SQL 2005.

Do you have a clean backup?

Once you've done the migation, be sure to update all the statistics and do a checkDB.

SQL 2005 can use the SQL 2000 statistics, but badly. Queries often run slower until...