Any other reason apart from what Henry has suggested above!

Try whats stated at-->http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx

MJ

Does the 90 day clock start counting from when I changed the login?

Yes. From the day you change the password..

If you don't find anything useful in logs then try running the backup command in ssms manually to see if it o/p's any error..

MJ

Queuing isn't the best indicator, but Avg Disk Sec/Read and Avg Disk Sec/Write could be used.

Usual recommendations for those counters are 10-50ms.

MJ

Got this from this forum-->

SQL Recon from Special Ops Security is free and does a great job as well as doing some quick analysis like blank passwords and a best...

For object level permissions:

--SQL 2005 ONLY

--This script will generate all user permissions and the code to

recreate them as required.

SELECT C.name 'Schema',

...

Try:

SELECT s.name AS schema_name, o.name AS table_name, i.name AS index_name,

ps.partition_number, ps.avg_fragmentation_in_percent, ps.avg_page_space_used_in_percent, ps.fragment_count, ps.page_count

FROM sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL, NULL, 'limited') ps

...

On similar lines of Lowell:

Try this:

select

o1.name as Referencing_Object_name

, c1.name as referencing_column_Name

, o2.name as Referenced_Object_name

, c2.name as Referenced_Column_Name

, s.name as Constraint_name

from sysforeignkeys fk

inner join sysobjects o1 on fk.fkeyid = o1.id

inner join...

Run sp_spaceused under your database and post the results here.

MJ

Did you try the script that I posted above?

Manu

Try this script. I found it on this forum.

--see growth from backup size in pages.

DECLARE @dbname sysname

SET @dbname = DB_NAME()

SELECT CONVERT(char, backup_start_date, 111) AS [Date], --yyyy/mm/dd format

CONVERT(char,...

Maybe a reboot will help. Not sure why its not displaying rest of the features.

If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup

You might have to re-create the publication as indicated...

Nice step by step illustration at-->http://blogs.msdn.com/sqlserverfaq/archive/2009/03/31/setting-up-database-mirroring-in-sql-server-2008-using-t-sql-when-the-database-is-encrypted-using-transparent-data-encryption.aspx

MJ