Have you considered log shipping or database mirroring? Check out BOL/TechNet for more information.

What build are you at? i.e.

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

Are you able to reproduce outside of management studio?

i.e.

USE [master]

GO

ALTER DATABASE [AdventureWorks] MODIFY FILE ( NAME = N'AdventureWorks_Data', FILEGROWTH...

Sounds like your on x64, if this is the case you might try the x64 install package 🙂

For clarification, the new disk volumes/resources are online and in the same cluster group as the SQL Server resource, correct? Also, is the SQL Server resource dependent on the new...

What build are you running i.e. -

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

Codeplex now maintains the AdventureWorks sample databases. Are you using the latest rev (for SP2a)? i.e. http://www.codeplex.com/MSFTDBProdSamples/Release/ProjectReleases.aspx?ReleaseId=4004

Try -

declare @cmd varchar(1000), @DatabaseTEMP varchar(1000)

set @DATABASETEMP = 'C:\program files\Microsoft SQL Server\MSSQL.1\MSSQL\Data'

set @cmd = 'osql.exe -E -Q "EXEC sp_attach_db ''EZSalesOrder'', ''' + @DATABASETEMP + '\EZSalesOrder_Data.mdf'', ''' + @DATABASETEMP +...

To drop the catalog (do this first) -

DROP FULLTEXT CATALOG catalog_name

Then try the steps above again.

To determine SP level -

SELECT SERVERPROPERTY('productversion'),

SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

Should be...

Have you updated statistics with a fullscan (i.e. index and column stats)?

Haven't seen that one. Are you running SP2? SMO issues within management studio can typically be alleviated by shutting down managment studio and reopening it. You can drop the...

You should just be able to drop the old one and create a new one; good step-by-step article w/ illustrations.

http://www.userscape.com/helpdesk/index.php?pg=kb.page&id=142

Correct however something to keep in mind. The example above will use a SHRINKFILE to take the log down to 1MB or so which on an OLTP system wouldn't be...

My apologies - thought this was a 2000 post 🙂

Much easier in 2005 - see this article -

http://msdn2.microsoft.com/en-us/library/ms142511.aspx

Corey Bunch wrote a good article on this -

http://www.sqlservercentral.com/articles/Administration/introtodatabasemailinsql2005/2197/

This might help -

Troubleshooting Server and Database Connection Problems

http://technet.microsoft.com/en-us/library/ms156468.aspx