You removed the subscriptions and publication but db is still enable for replication...

Run the script Corlos suggested or you can use EM to disable replication...

Upgrade from 32bit 64 bit is not a problem... you can do backup restore or detach attach...

I have not seen any problem but it always better testing specially applications.....

test..test..test... move...

Better check with MS about licencing info...

http://www.microsoft.com/sql/howtobuy/default.mspx

I will not worry who controls the backup ... I will be more interested how eficient and reliable they are....

I believ most of these backup solutions are pretty good for...

You can't accomplish with one MP configured for all...

You have to create diffent MPs one for each process (backup, checkdb, reindex...)...

OR

You can create a job using tsql without using MP...

I...

I don't have the URL handy but you can go to microsoft.com and register for updates...

The following articles will help you to do what you want...

http://www.devx.com/dbzone/Article/31648

http://www.databasejournal.com/features/mssql/article.php/3611426

Yes and table should not have LOB columns (text, ntext, image...)...

What edition of sql server 2005 you are trying to connect?

By default remote connections are disabled in Express/developer editions...

Open Surface Area Configuration and check for remote connections option is enabled...

Again some one else in the db...

When you rename the database, sql will try to get the exclusive on the db so that it can rename it..

You can use my...

For some reason they removed...no idea why... you may try exporting into excel and convert excel into dbase/faxpro...

Just google for "excel to dbase convertion"

You suppose to add it in merge agent job not in profile... if I am not mistaken...

Did you change the configuration in merge agent job?

Try after disabling the publication property on the "subscription options".. Under Schema replication...Replication schema chanes.. make this option to FALSE and then create the trigger...by default this property is TRUE...

I don't think that is the case...

Try creating the linked server before configuring replication..

You can rollover the files when it reaches certain size then read all files except the one in use...

If you make rollover size is smaller ...

Note: You configure the profiler...