Can you install the tool on a 32bit OS and then connect to the 64-bit server you wish to script out?

Ran into this issue years ago with an even number of processors but not a power of 2.

4 sockets with 6 cores each = 24 logical.

I would vote for option 2 as well.

You could upgrade your mirror server to Windows/SQL 2008R2.

Rebuild mirroring from the 2005 cluster to the 2008R2 machine.

Failover and run on the standalone...

Why not just create another version of sp_helpdb based on the system stored proc? Something like this:

USE [master]

GO

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

CREATE procedure [dbo].[sp_help_db] -- 1995/12/20 15:34 #12755

@dbname sysname...

Try:

EXEC sp_changedbowner 'sa'

Was this database upgraded from SQL 2000? I would try running DBCC UPDATEUSAGE and then rerunning the first query. The first query appears correct to me.

Might also be a global temp table.

To assess memory pressure you need to look at SQL Server:Buffer Manager and the counters

Buffer Cache Hit Ratio (should be > 90) This is the % of pages in memory...

The perfmon counter SQL Server:Memory Manager:Total Server Memory(KB) will tell you exactly how much memory SQL is using.

Paul Randal explains it better than anyone.

http://technet.microsoft.com/en-us/magazine/2009.02.logging.aspx

Yes, you can do remote scans with it.

A good starting point would be the SQL Server Best Practices Analyzer since it's free.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0fd439d7-4bff-4df7-a52f-9a1be8725591

Since the database is already in full recovery, I assume you are already running tlog backups every 15 min. You can query msdb.dbo.backupset to pull the transaction log backup sizes.

SELECT...

AWE is not needed for 64-bit systems, however, you should configure lock pages in memory.

From the article below:

AWE is not required and cannot be configured on 64-bit operating systems.

http://msdn.microsoft.com/en-us/library/ms190673.aspx

As a production DBA about 50-60% of my time is self-directed.