I ran into something like this too.  I think I solved it by restarting my MSSQLSERVER service.  I also had to make sure to install the developer edition of the...

I agree.  I got the question right, but it works with the default settings only.  I thought the question would be about the ANSI NULL settings, obviously that affects the...

Cool!  We can comment on how bad/poorly worded/poorly edited the questions are before they're published!

Yes and no.  That is,  SSIS can be part of a solution, but if you want two-way synchronization with two live databases, you will need some sort of mechanism to...

This refers to database mirroring, which is not going to be a part of SQL 2k5 release.

This was fixed in SP4, at least for me.

sp_defaultdb [ @loginame = ] 'login' ,

    [ @defdb = ] 'database'

HTH

Someone needs to edit these questions and answers.  This is the third time in recent weeks that the answer has been incorrect.  Especially the backup questions seem to be mixed...

That was my conclusion also.  Since I didn't see 7 as an option I figured 6 was closest.  Who worries about the private network?  Yes you have to set those...

If you must get @@version to show > .760, you can install one of the post SP3 hotfixes to get it up to .818 or higher.

I don't know specifically why the conflict viewer won't work, but the conflict data is stored in conflict tables in the publication DB.  You can check there manually.  For example: ...

I have found this to be very useful, when dealing with over 300 connections:

sp_who2 'active'

...gives a list of active connections, ones where activity is not 'AWAITING COMMAND'

I was thinking of where you suggested:

if Object_id(tempdb..#tempTable)>0...

This will only work in the connection that created the temp table...since he was looking for it in EM I thought I should...

Ah, sushila, I missed where you said, run this in tempdb.  Some people try looking in the local db.

We use merge replication in a similar scenario, though we have many more transactions.  It doesn't scale well to our size, about 300 GB of data/indexes.  But for smaller situations...