I personally wouldn't start with anything less than 8Gb for a small implementation.

You need to factor in database size(s), usage, OLAP/OLTP and performance requirements as a starting point.

Just run the tool on a server without SQL installed...you shouldn't have that problem then.

It looks like it is running the wrong application. I'm not sure why.

I would try and install on a workstation (just ensure you have admin rights on the destination server)...

You had the name right, wrong tool 🙂

http://www.microsoft.com/downloads/details.aspx?FamilyID=1470e86b-7e05-4322-a677-95ab44f12d75&displaylang=en

Um, actually it has all the information if I remember correctly. allocated and reserved space of the database...

You are running the wrong tool 🙂

That is the upgrade wizard rather than upgrade analyzer. If I remember correctly, designed to upgrade from 6.5 or 7 to SQL 2000.

You must...

What script are we talking? You could do it in DOS using a batch file, right?

Did you try using sp_spaceused?

You sure it's pointing at the correct instance?

You could try the SQL 2008 advisor (as it will identify the same issues as SQL 2005 advisor).

I would take a different approach and go straight for the SQL 2008 certification.

Our company is taking the opposite approach and skipping over SQL 2005 (from SQL 2000) as...

Have you tried temporarily disabling foreign key constraint checking?

There are many tools!

I have used Spotlight on SQL Server in the past, but it used quite a bit of resources at times.

I like doing things manually and just...

Sorry- I meant Lee...bed time:blush:

Agree with SQLRocker. Performance can fluctuate significantly from my experience due to shared disk and server resources.

HP's PolyServe looks like an interesting option for virtualization...

Sorry- User Acceptance Testing or Development environments, rather than Production.