refer the following link for monitoring:

http://msdn.microsoft.com/en-us/library/ms190224.aspx

Hello,

Solution is very simple you need to copy the code to query analyzer and change the database to "production" and than execute the script.

HTH

Already John has mention:

BOL Topic “ALTER SCHEMA (Transact-SQL)”.

system shcema could not change.

If possible you can stop and start services "SQL Browser".

Default instance should not be a problem to set up the logshipping. More detail about your issue will help to guide you.

In my openion, it doesn't make much differnece if you cahnge before or after the upgrade.

On Database side it's very easy to change the dbname. But more work needs...

In BOL; I do not found status value like 4194320, 4194328.

What is the status of the database?

In SQL Server Agent Create Operators and in Notification options-Email nme: write the e-mail address by seperating ";"

e.g. email1@email.com; email2@email.com etc.

Simply Assign this operator to notify.

What is the recovery mode of your database? Is your database accessible?

I guess; "A user to act like another user"

looks correct answer as per the following MS article:

http://msdn.microsoft.com/en-us/library/ms188304.aspx

In addition to the above, I guess Replication do not require index on all the columns. But it require a Cluster Index to get the article replicated.

Check the credentials and findout job owner is having access to FTP.

Think about composit index.

You can also check if any opent transactions are there or not?

Hello Rechard,

You can also think about the new feature of SQL Server 2008 "Compress Backup" to save disk space & time.

Also if you are not using 2008 than you can...