Hi,
Now, I've installed SQL Server 2000 standard edition, and
I've registered the Remote Computer in my Enterprise
Manager. How ever when I run the "Create Publication
Wizard", I get an Information Message, that:
"SQL Server Agent on 'MyComputer' currently uses the
system account, which causes replication between servers
to fail. In the follwing dialog box, specify another
account for the service startup acccout".
Anyway, once I press OK, I come through a Dialog Box
called "SQL Server Agent Properties - MyComputer", where
in the General Tab "Service Startup Account" is disabled.
After I ignore it and come through another Dialog Box
called "Specify Snaphsot Folder". In that Dialog box, the
default value
was "\\RemoteComputer\C$.....\MSSQL\ReplData", but I do
get another Information Message as saying:
"'\\RemoteComputer\C$.....\MSSQL\ReplData' is not a valid
path, or it referes to a file isntead of folder. Enter
the Path to an existing folder." And this doesn't give to
go through the Wizard.
Why this is happening? how can I use Enterprise Manager
from another computer to configure Replication Scenario's
to a computer with MSDE 2000 Installed, Else If i Cant use
enterprise Manager, how can I use the osql tool to
configure replication. The SQL books online is Complicated
on osql, so please help me by telling how would you
configure this replication without Enterprise Manager on
Computer with only MSDE 2000 installed?
Regards,
Nazeer.
NOTE: My computers are connected to a LAN
Nazeer,
if you're replicating to another computer you'll need to do 2 things:
(1) go to control panel, administrative tools, services and select the sql
server agent service. Change the startup account to a domain user. To make
things easy, put this account in the local admin's group (assuming
builtin/administrators are in sysadmin also on sqlserver). Do the same on
the subscriber, preferably with the same account. This is not the most
granular way to set things up, and for more detailed info, have a look in
the replication, security section of BOL. Initially let's just ensure you
can get this up and working.
(2) on the publisher share the repldata folder as \\computername\repldata
and configure replication to use this share (right-click replication
monitor, distributor properties, publishers tab, publisher elipsis...).
HTH,
Paul bison
|||Hi Paul,
Thanx for your solution, it did work out correctly. OK,
there's one more problem,
In case, If the Publisher is a MSDE 2000, how am I gone to
create a publications, subsribtions etc.? and what is ment
by "Row guide column"?
Nazeer,
>--Original Message--
>Nazeer,
>if you're replicating to another computer you'll need to
do 2 things:
>(1) go to control panel, administrative tools, services
and select the sql
>server agent service. Change the startup account to a
domain user. To make
>things easy, put this account in the local admin's group
(assuming
>builtin/administrators are in sysadmin also on
sqlserver). Do the same on
>the subscriber, preferably with the same account. This is
not the most
>granular way to set things up, and for more detailed
info, have a look in
>the replication, security section of BOL. Initially let's
just ensure you
>can get this up and working.
>(2) on the publisher share the repldata folder as
\\computername\repldata
>and configure replication to use this share (right-click
replication
>monitor, distributor properties, publishers tab,
publisher elipsis...).
>HTH,
>Paul bison
>
>.
>
|||Nazeer,
if you're using MSDE, you could use SQLDMO if you wanted to create the
publication programatically. If you need to do it graphically, the MSDE can
potentially be administered from Enterprise Manager - however, please first
check the licensing documents as I'm not too sure if this is permitted or
not. If you need to create a subscription on the MSDE box , you could use
windows synchronization manager.
GUIDS are used in merge replication and updating subscriber scenarios. Merge
will create a rowguid column or use an existing column having the rowguid
attribute. In merge the guid doesn't change while it does for updating
subscribers but still, they are essentially just unique identifiers for a
row.
HTH,
Paul Ibison
|||I suggest you use the replication ActiveX controls as they have methods in
them which allow you to connect to the Publisher without having to register
the subscribers in EM or using Client Network Utility.
If you use SQL DMO you will still have to use Client Network Utility which
is a violation of your licensing agreement for MSDE.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23quBWZffEHA.712@.TK2MSFTNGP09.phx.gbl...
> Nazeer,
> if you're using MSDE, you could use SQLDMO if you wanted to create the
> publication programatically. If you need to do it graphically, the MSDE
can
> potentially be administered from Enterprise Manager - however, please
first
> check the licensing documents as I'm not too sure if this is permitted or
> not. If you need to create a subscription on the MSDE box , you could use
> windows synchronization manager.
> GUIDS are used in merge replication and updating subscriber scenarios.
Merge
> will create a rowguid column or use an existing column having the rowguid
> attribute. In merge the guid doesn't change while it does for updating
> subscribers but still, they are essentially just unique identifiers for a
> row.
> HTH,
> Paul Ibison
>
|||Hi,
I just want to know, is it possible to replicate some
certain entries only. Now say, that there is a Server
(assume that it's called as MiniServer) which
Maintains "Purchase Orders". This Purchase Orders' Primary
Key is "OrderID" and it's an autoincremental field. Also
this MiniServer's Purchase Order Table's Last OrderID
value is 50. This MiniServer Replicates it's Data to the
MainServer at the end of Each office days.
Just note that the MainServer's Purchase Order Table has
it's Last OrderID = 25, and the MainServer needs all the
OrderID more than 25 from the MiniServer.Is this possible
with Replication? If so, how can I set it in SQL Server
Replication?
Awaiting your Response in Anticipation.
Thanx in Advance.
HIFNI NAZEER
>--Original Message--
>Nazeer,
>if you're using MSDE, you could use SQLDMO if you wanted
to create the
>publication programatically. If you need to do it
graphically, the MSDE can
>potentially be administered from Enterprise Manager -
however, please first
>check the licensing documents as I'm not too sure if this
is permitted or
>not. If you need to create a subscription on the MSDE
box , you could use
>windows synchronization manager.
>GUIDS are used in merge replication and updating
subscriber scenarios. Merge
>will create a rowguid column or use an existing column
having the rowguid
>attribute. In merge the guid doesn't change while it does
for updating
>subscribers but still, they are essentially just unique
identifiers for a
>row.
>HTH,
>Paul Ibison
>
>.
>
|||Hifni,
with merge replication, the it is not normally so difficult to achieve this
setup.
If you were using merge replication, only those records not yet transferred
from MiniServer to MainServer will be replicated, so if 1-25 originated from
MiniServer and are now on MainServer, they won't be replicated again. If the
records 1-25 came originally from MainServer and are now on MiniServer, they
won't be cycled backwards to MainServer, unless they have been modified on
MiniServer.
BTW there is no possibility of (identity & PK) OrderIDs overlapping - they
are partitioned into ranges either during the publication setup or manually.
HTH,
Paul Ibison
). Do you have 1434 blocked? If