Merge replication can be one of the option . But you have to manage conflict if any occur proactively.

You can Read details about Merge replication online http://msdn.microsoft.com/en-us/library/ms151329(v=sql.105).aspx

Regards

Dhananjay

What changes you have done... Have u added user running SQL services for Loack pages in memory seetings and restart sql services.

hope this will work...

You need to allow updates in system table by executing below command.

sp_configure 'allow updates',1

RECONFIGURE WITH OVERRIDE

cheers!!!

you can run update query on sys.comments table in sql 2005 or syscomments in sql 2000. it may solve uor problem.

cheers

Hi,

Why don't you try in-built log-shipping of SQL server or even replication... Believe me its very easy to setup and manage.... Any one can manage it whenever u will be...

What is size and volume of database that needs to be replicated.

I am not completely agree with you that :- Your DBA perform Index maintainance task for Oracle once in six months and perform same task in sql very often (daily...

Hi,

You can use dbcc sqlperf(logspace).

Regards

Dhananjay

Lock Pages in Memory setting is required when you are using 64 bit edition.

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

You need to update the stats after re-index or index-defrag. Try running sp_updatests .....

Have you checked whether Windows is showing all 40GB of RAM. Check and confirm.

Primary Key is must for table Participating in Transaction Replication.

Hi Narender,

you can schedule your Backup on Network drive. This will be common to all the node. I don't find there is any issue in that. Even we have databases...

Check this document... may this will help you....

There will not be any issue... are u maintaining witness as standalone server or on same server