Check the BOL topic "Executing Scripts Before and After the Snapshot is Applied"

You can specify the scripts to run before and/or after snapshot...it is very useful if some one want...

You may need to reinitialized snaphot after restore...

You need stop your replication before restore otherwise you may get the error database in use...

How to move SQL Server databases to a new location by using Detach and Attach functions in SQL Server

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

How to prepare SQL Server 2005 and SQL Server 2000 for changes to daylight saving time in 2007

http://support.microsoft.com/default.aspx?scid=kb;en-us;931975&sd=rss&spid=2855

In general you can't because memory is instance specific not the database specific...

You can try alternate routes using sysprocesses table and syscacheobjects tables but you don't get accurate value...

As Greg mentioned it could be anything be more specific...

ODBC tracing log file name also SQL.log but the path is "C:\DOCUME~1\User~1\LOCALS~1\Temp\SQL.LOG"

You can use the load balancing device like CISCO CSS for this...

Enable remote connections in SQL server 2005 Surface Area Configuration (SAC)...

Run the sql trace and enable error and warning and check for long running queries too...

Try the following in query window...

ALTER DATABASE [db name] MODIFY FILE ( NAME = N'Log file name', MAXSIZE = UNLIMITED)

It looks fine...

try running the backup without creating the disk...

Don't run the restore verify...first let backup finish completely...

BACKUP DATABASE [XYZ] FILEGROUP = N'PRIMARY' TO disk = 'D:\FT005.YINT01.USERDB BACKUP\XYZ\XYZ.BAK' WITH stats = 10,...

You can use native sql backup command to backup the databases and its transaction log backups...Or you can use the database maintenance plans wizard to create backups...

See BOL topic "Backup...

Why don't you use SSIS/DTS to copy objects and data from 2005 to 2000...

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

Read the following blog "Obtaining Statement-Level Query Plans "

http://blogs.msdn.com/sqlcat/Default.aspx?p=2

There were issues before sp2... It think in sp1...

MPs file cleanup was not working properly...in continuation to that definately you have to check all major jobs after applying SPs and...

I have applied to one server but it was successful.

I have not see this error in forums..

At what stage in sp2 process you are getting error?

What is your sp2 installation...