I am not certain you can do this. The reason for those dbs is so very important

Master

Purpose - Core system database to manage the SQL Server instance. In SQL...

When you say you are moving them over. Do you mean you are just going to take the backup and restore to 2005 and leave the compatibility at 80...

After you change all these items, I suggest you run BPA against your system to find out what else may be hampering your system for memory.

Just down load BPA and...

You should not be using this at all for an example like these at all. Everyone should be using Parameterized queries and using the column names when selecting fields...

Be carefull with the KISS approach. That is how we got into the SELECT * mentality in the first place.

Without coding standards, developers will code the way they have...

This example is good for the purpose of changing the mindset of many developers -- continuing the laziness of not putting column names and only using * for everything. ...

This is great information and easy to understand.

I have used it on over 100 of the 2000 dbs that I review

if you perform in 2005

deny select from sysobject to [specificuser who has sysadmin role]

it won't let you

question:

if your user has public and sysadmin, can you still deny 'Select'

are you already clustering?

I want to mention a document you might want to read before clustering.

Titled: Failover Clustering for Microsoft SQL Server 2005 and SQL Server 2005 Analysis Services

do...

can you point to why the space runs out so frequently?

maybe you just need to perform maintenance on the db.

awesome!

did anything work for you?

let's see what the space is really like

run

exec sp_spaceused @updateusage = 'TRUE'

this URL might help you

http://support.microsoft.com/kb/889654/

I would advise applying sp2 at a minimum to the Standard edition.

I requested the sp_helpdb [each db in question]

but have not received any answer yet.