Another thought I had was to look at the 'setup bootstrap\log' directory to see what history is out there. I believe the history is maintained, but I don't recall...

As long as all of the SQL cluster requirements are met there is no issue running different versions of SQL on the same cluster.

I'd apply, SP3, CU5, then the specific security patch that you have noted. I'm not sure if the add/remove programs shows the CUs or not - you could check...

On this site - lists the build lists:

http://www.sqlservercentral.com/articles/Administration/2960/

I'd also suggest redownloading the ISO and trying Grants process of extracting the install via an ISO reader directly to the hardware where you're trying to install to.

Just curious if you burned the download to a regular DVD. The .iso is too large to fit on a standard DVD and if you didn't notice it, this...

I suspect the timeouts are due to the fact that unallocated space is a negative number which is preventing the database from growing at all. There was / is...

execute sp_spaceused for the database in question and look to see whether or not the allocated space shows as a negative number. This can prevent the database from allocating...

There is an issue with SQL 2000 that reports space as a negative number when looking at sp_spaceused and also causes the database not to grow automatically due to this....

And there you have your answer. GRANT CONTROL ON SCHEMA dbo essentially gives full control to the dbo schema and supercedes the db_datareader database role.

It always helps if you include your table and the code you're using so we can see the actual issue. However, it appears that you are inserting into a...

You'll have to create a new database with just the single data file and export / import the data from the old database to the new one. There are...

You're probably already aware of this, but ff you're constantly adding new databases to this server, just add the credentials to the model database as well and any new database...

Go to the Job Activity Monitor and ctrl-left click on each, then right click and select disable job, or you can write a script against msdb.dbo.sysjobs and update the enabled...

Is it the primary file group? If so, it can't be removed regardless of whether it's empty or not.