Remote-server registration

Does MSDE support registering a (remote) sql-server.
I am trying to replicate between two computers on the Internet (both XP).
Is this a futile attempt ... must the publisher be a "full" instance of SQL
server?
check out this link:
http://support.microsoft.com/default...;en-us;Q324992
MSDE 2000 can act as both a Publisher or Distributor, and a Subscriber, and it can replicate between MSDE versions and regular versions of SQL Server. Additionally, you cannot use it for transactional publication, but you can use it as a Publisher of snap
shot replication, and merge replication, and as a Subscriber to all three types of publications.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" wrote:

> Does MSDE support registering a (remote) sql-server.
> I am trying to replicate between two computers on the Internet (both XP).
> Is this a futile attempt ... must the publisher be a "full" instance of SQL
> server?
>
>
sql

Remote Laptop SA Password

Hi All,

We have remote users using sql server 7 on laptops. They use a vb app and replicate with the main server.

I have just discovered they have weak passwords on their sa account.
Others are suggesting that the laptops do not need strong passwords for their sa account as they are only subscribers . Are they talking rubbish?

Thanks,
JJCYou may want to give a look at the article in BOL about xp_cmdshell. Basically, if a dba (or many programmers for that matter) can get your sa password, that dba/programmer can own your laptop. There was a virus that searched the internet for SQL Servers that had no sa password, and it was shockingly effective.

If the laptops are only subscribers, and you do not allow anonymous pull subscriptions, you should be ok at the central server, but those laptops really should have their security beefed up.|||END USERS SHOULD NOT BE USING SA ACCOUNTS!

Even DBAs shouldn't be using the SA account!

Even System Administrators should not use the SA account! They should set up an account that grants themselves only the permissions necessary to do their day-to-day tasks, and only log in as SA when absolutely necessary. Otherwise, sooner or later you WILL do something you wish that you hadn't. Don't think of user accounts as restricitions. Think of them as safeguards!

Give all your users SQL logins or NT logins, and then change your sa password.

blindman|||If possible, set your users' laptops to Windows Authentication only. This way you'll come out clean without having to remember each laptop's SA password, or having to create a user on each laptop.