Are you able to locate "xprepl.dll" on your server? If not then it seems your sql installation has got sum problem try to repair or reinstall it

MJ

Try this:

USE master

GO

/****** Object: StoredProcedure [dbo].[sp_GetSpaceUsedByDBs] Script Date: 03/12/2009 14:41:23 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

Create procedure [dbo].[sp_GetSpaceUsedByDBs]

as

create table #ls (name varchar(255), LogSize real, LogSpaceUsed real, Status...

SQL Server (2000, 2005, 2008): Recovery/Rollback Taking Longer Than Expected

(Microsoft PSS Guys Comments)

Interesting discussion around rollback. The transaction has run for 14 hours and then a KILL SPID was...

In my case when I am trying to save the newly created plan(copy of old plan as u suggested) its not creating the job and failing with message "Rename failed...

Did you use upgrade advisor before going for upgrade?

http://msdn.microsoft.com/en-us/library/ms144256(SQL.90).aspx

MJ

When--> Check the binn directory creation date and by "Whom" I think that can be answered either by checking event viewer logs/sql installation log file(not sure).

MJ

What's the error message that you receive while restoring?

MJ

Have you checked-->

http://blogs.msdn.com/sqlserverfaq/archive/2009/01/09/sql-server-2005-sp3-install-fails-with-error-1612-unable-to-install-windows-installer-msp-file.aspx

MJ

It can't be done. Stated at-->http://www.sqlservercentral.com/Forums/Topic638206-146-1.aspx?Update=1

MJ

Creating multiple log files for the same database doesn't seem to help anything unless disk space is an issue.

MJ

Check--> http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/5ce5ef27-7311-4477-9b48-5f3553fa3c9c/

The work-around is to edit the INSTMSDB.SQL script and change two instances of Yukon90_ to something more complex. In my case, I used: 1qaz@WSX3edc$RFV

MJ

Why don't you try this: Create a new filegroup with same name "NEW" in your case under the same database and then try deletng it. Hopefully it should delete the...

It doesn't look CU 10 or CU 11 were applied:

Check for "Build 09.00.3077" at

-->http://support.microsoft.com/default.aspx/kb/937137/en-us#

MJ

Googling helps:

To determine whether or not Service Broker is enabled for a particular database, execute the following T-SQL:

SELECT is_broker_enabled FROM sys.databases WHERE name = 'Database name';

-- Enable Service Broker:

ALTER...

Make use of stored procs. like EXEC master.dbo.xp_backup_database and EXEC master.dbo.xp_restore_database as listed at -->http://vyaskn.tripod.com/backup_and_restore_with_sql_litespeed.htm

MJ