Replication to trusted domain - naming convention problem?

We have a domain, say OUR_DOMAIN. Within this I replication running happily
for several months from MYSQLSERVER . We now have another "trusted" domain
at a co-location, OTHERDOMAIN.
To see a machine from the other I need to use MYSQLSERVER.OUR_DOMAIN.
However, when I set up a pull replication from the OTHERDOMAIN machine, say
MYSQLSUB, the task fails trying to connect to MYSQLSERVER, even though I
refer to it as MYSQLSERVER.OUR_DOMAIN.
The Pull subscription is created properly, and I go to the job list and run
the job. The step is
-Publisher MYSQLSERVER-PublisherDB [PublishDB] -Publication
[MyPubName] -Distributor [MYSQLSERVER] -SubscriptionType 1 -Subscriber
[MYSQLSUB] -SubscriberSecurityMode 1 -SubscriberDB [MyDBName]
However it is unable to connect, The process could not connect to
Distributor 'MYSQLSERVER'.
If I change the job to be publisher MYSQLSERVER.OUR_DOMAIN then I get the
error "The process could not retrieve security information from the
Subscriber for Distributor 'MYSQLSERVER'. The step failed." Which suggests
adding the domain to the publisher worked. However if I add the domain to
the distributor
-Publisher MYSQLSERVER.OUR_DOMAIN-PublisherDB [PublishDB] -Publication
[MyPubName] -Distributor [MYSQLSERVER.OUR_DOMAIN] -SubscriptionType
1 -Subscriber [MYSQLSUB] -SubscriberSecurityMode 1 -SubscriberDB [MyDBName]
I get "The process could not retrieve security information from the
Subscriber for Distributor MYSQLSERVER.OUR_DOMAIN'. The step failed."
Both agents are running under administrator level accounts on their
respective domains, and the subscriber account is in the Publication Access
List.
Any help with naming conventions used here or any resources or pointers
would be greatly appreciated.
Cheers!
Simon
I prefer to use NetBIOS names to register the servers in EM. Then I hide the
FQDN or the IP address of the server using Client Network Utility. I then
use a single account in both domains with the same password to connect to
both server and I also use this account to run the SQL Server agent account
under.
So on OUR_Domain the account would be SimonCar and the password could be
Racnomis. On OtherDomain the account would be SimonCar and the password
could be Racnomis. Another option is to use local machine accounts with the
same name and password.
A third option is to use SQL Server authentication.
One final point is that a patch has changed the way agent security works.
You must now run the agents with the SA job owner.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Simon" <simoncar@.NotThisBittotalise.co.uk> wrote in message
news:%23LmtjUb8FHA.3132@.TK2MSFTNGP12.phx.gbl...
> We have a domain, say OUR_DOMAIN. Within this I replication running
> happily for several months from MYSQLSERVER . We now have another
> "trusted" domain at a co-location, OTHERDOMAIN.
> To see a machine from the other I need to use MYSQLSERVER.OUR_DOMAIN.
> However, when I set up a pull replication from the OTHERDOMAIN machine,
> say MYSQLSUB, the task fails trying to connect to MYSQLSERVER, even
> though I refer to it as MYSQLSERVER.OUR_DOMAIN.
> The Pull subscription is created properly, and I go to the job list and
> run the job. The step is
> -Publisher MYSQLSERVER-PublisherDB [PublishDB] -Publication
> [MyPubName] -Distributor [MYSQLSERVER] -SubscriptionType 1 -Subscriber
> [MYSQLSUB] -SubscriberSecurityMode 1 -SubscriberDB [MyDBName]
> However it is unable to connect, The process could not connect to
> Distributor 'MYSQLSERVER'.
> If I change the job to be publisher MYSQLSERVER.OUR_DOMAIN then I get the
> error "The process could not retrieve security information from the
> Subscriber for Distributor 'MYSQLSERVER'. The step failed." Which
> suggests adding the domain to the publisher worked. However if I add the
> domain to the distributor
> -Publisher MYSQLSERVER.OUR_DOMAIN-PublisherDB [PublishDB] -Publication
> [MyPubName] -Distributor [MYSQLSERVER.OUR_DOMAIN] -SubscriptionType
> 1 -Subscriber [MYSQLSUB] -SubscriberSecurityMode 1 -SubscriberDB
> [MyDBName]
> I get "The process could not retrieve security information from the
> Subscriber for Distributor MYSQLSERVER.OUR_DOMAIN'. The step failed."
> Both agents are running under administrator level accounts on their
> respective domains, and the subscriber account is in the Publication
> Access List.
> Any help with naming conventions used here or any resources or pointers
> would be greatly appreciated.
> Cheers!
> Simon
>
>
|||Hilary Cotter wrote:
> I prefer to use NetBIOS names to register the servers in EM. Then I
> hide the FQDN or the IP address of the server using Client Network
> Utility. I then use a single account in both domains with the same
> password to connect to both server and I also use this account to run
> the SQL Server agent account under.
> So on OUR_Domain the account would be SimonCar and the password could
> be Racnomis. On OtherDomain the account would be SimonCar and the
> password could be Racnomis. Another option is to use local machine
> accounts with the same name and password.
> A third option is to use SQL Server authentication.
>
The network guy has now set it so I can use just <servername>. I have set
the ReplData to be a share and point to that from the subscriber (it has
permissions to this share). The <Otherservername> is in the list of
subscribers but SQL claims it isn't from <Otherservername> when I request a
Pull subscription, but if I allow anonymous I can get it replicating fine.
The only downside of that I am aware of is the retention of replicated
transactions if I allow anonymous?
The same user/password seems simple enough for me to appreciate!
Thanks for your help.
Cheers!
Simon
|||> The <Otherservername> is in the
> list of subscribers but SQL claims it isn't from <Otherservername>
> when I request a Pull subscription, but if I allow anonymous I can
> get it replicating fine. The only downside of that I am aware of is
> the retention of replicated transactions if I allow anonymous?
There is some connectivity/authentication issue still here becuause if I add
the subscriber to the publisher from a copy of EM on the subscriber it
works, if I add the subscriber to subscribers through EM from my machine or
the publisher it doesn't recognise it even though the same machine name is
used.

Replication to a web server in DMZ

Hello,
We have active/active SQL2000 SP3a on a Win2k3 cluster in our domain. We
need to copy some tables from a
database out to our web server.
The web server, is SQL2000 SP3a on Windows 2000, SP4. It is a stand-alone
server out in the DMZ.
We get the following error when trying to do this:
SubSystem Message - Job 'VIRTUALSERVERNAME\INSTANCENAME-WEBSERVER-13'
(0x5F1388610429AD4B8860D51DF8504198), step 2 - Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection. The
process could not connect to Subscriber 'WEBSERVER'.
Here are some thoughts we have. The SQL server in the domain runs on port
1303. The SQL server in the DMZ is running on a different port. Do the
ports need to match for the replication to occur?
We are not sure why this isn't working. Anyone have some input or some
documentation on how to set up replication to a web server in a DMZ. I am
sure this is something that is done at most companies, but we are missing
something.
Thanks in advance.
Hopefully this article will help out:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I would try SQL Authentication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JJP" <anonymous@.discussions.microsoft.com> wrote in message
news:%23%23dsWsu6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Hello,
> We have active/active SQL2000 SP3a on a Win2k3 cluster in our domain. We
> need to copy some tables from a
> database out to our web server.
> The web server, is SQL2000 SP3a on Windows 2000, SP4. It is a stand-alone
> server out in the DMZ.
> We get the following error when trying to do this:
> --
> SubSystem Message - Job 'VIRTUALSERVERNAME\INSTANCENAME-WEBSERVER-13'
> (0x5F1388610429AD4B8860D51DF8504198), step 2 - Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection. The
> process could not connect to Subscriber 'WEBSERVER'.
> --
> Here are some thoughts we have. The SQL server in the domain runs on port
> 1303. The SQL server in the DMZ is running on a different port. Do the
> ports need to match for the replication to occur?
> We are not sure why this isn't working. Anyone have some input or some
> documentation on how to set up replication to a web server in a DMZ. I am
> sure this is something that is done at most companies, but we are missing
> something.
> Thanks in advance.
>
|||Thanks Paul, I am looking that over.
Hilary, the web server is using Windows and SQL, is that what you are
referring to?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ORJz63u6FHA.3416@.TK2MSFTNGP15.phx.gbl...
>I would try SQL Authentication.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "JJP" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23%23dsWsu6FHA.1276@.TK2MSFTNGP09.phx.gbl...
>
sql

Replication through VPN successful??

In the office network domain I've already setup replication between two SQL
Servers( SQL11Server & SQL22Server). Now I am extending replication with SQL
servers in other non-trusted domains/workgroups (SQL33Server & SQL44Server).
SQL33Server & SQL44Server are in non-trusted domains connecting to the
office via VPN. SQL33Server can ping SQL11Server.mydomain.local fine,
but it cannot ping just SQL11Server. Is this going to be a problem if it
pings the full DNS address?
When I started MAKEPIPE on SQL11Server, from SQL33Server I have to type
READPIPE /Ssql11server.mydomain.local for it to work. If I type READPIPE
/Ssql11Server it doesn't work..
Do I have a NETBIOS resolution problem ' Or what is the problem and how can
I successful established the connections through VPN? What the steps I
must take to established a successful VPN replication?use a host file for this.
For instance your host file should contain this entry
123.345.567.678 SQL11Server
replacing the numbers with your IP address for SQL11Server
If a netbios name has a . in it, the resolution will be using DNS. It should
like your name resolution service (probably WINS) can figure out where
SQL111Server is.
"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:utbkWlm%23DHA.2664@.TK2MSFTNGP09.phx.gbl...
> In the office network domain I've already setup replication between two
SQL
> Servers( SQL11Server & SQL22Server). Now I am extending replication with
SQL
> servers in other non-trusted domains/workgroups (SQL33Server &
SQL44Server).
> SQL33Server & SQL44Server are in non-trusted domains connecting to the
> office via VPN. SQL33Server can ping SQL11Server.mydomain.local fine,
> but it cannot ping just SQL11Server. Is this going to be a problem if it
> pings the full DNS address?
> When I started MAKEPIPE on SQL11Server, from SQL33Server I have to type
> READPIPE /Ssql11server.mydomain.local for it to work. If I type
READPIPE
> /Ssql11Server it doesn't work..
> Do I have a NETBIOS resolution problem ' Or what is the problem and how
can
> I successful established the connections through VPN? What the steps I
> must take to established a successful VPN replication?
>
>

Replication security help please...

Hello,

I am being told that my SQL server can no longer use a domain account to do replication cause it is a violation of SOX codes... So here is my question to ease my pain....

I believe that I can run the SQL server service under [local system account] with no issues but what about the SQL server agent service?

It needs rights on all the servers right?

I have found where you can configure replication to use sql authentication but then I can use snapshots...

any help would be appriciated...

oh.. I use transactional and merge if that makes any difference.

Hi William,

Replication agents run under the context of a Windows account. The agents make Windows Integrated Security connections by using this account. The account under which the agent runs depends on how the agent is started. If you start the agent from a SQL Server Agent job, the default: When a SQL Server Agent job is used to start a replication agent, the agent runs under the context of an account that you specify when you configure replication.

So SQL server agent service account do not need rights on all the servers, it could be local system account as well.

Hope it helps.

Wanwen

|||

So if I change SQL agent to run as system account but change replication to run as an account that does have access to all servers that have replication, then this should work?

|||

Yes, Please remember to change SQL agent service account through SQL server configuration manager.

Wanwen

Replication over the Internet - Resolving server name

We are using anonymouse pull subscriptions over the internet. We are not
using VPN.
The physical SQL Server is called SQL22Server. We have a Domain assigned to
it called something like company.com.
However, I found that on the client machine, I had to put in a hosts entry
to route SQL22Server to the IP address. I was hoping I could just use the
domain name.
This creates an administrative overhead because we have to do add a host
entry during the client install instead of having just assigning value to the
merge object.
If I try the domain, the error I get is: The remote server does not exist or
has not been designated as a valid Publisher.
I created the replication using the SQL22Server name.
Thanks,
Buzz
use the activeX scripts to deploy your subscriptions. In it there are
PublisherNetwork, DistributorNetwork, PublisherAddress, and
DistributorAddress properties. These map to the entries you would otherwise
put in your CNU or hosts file to make this work.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Buzz" <buzz@.online.nospam> wrote in message
news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> We are using anonymouse pull subscriptions over the internet. We are not
> using VPN.
> The physical SQL Server is called SQL22Server. We have a Domain assigned
to
> it called something like company.com.
> However, I found that on the client machine, I had to put in a hosts entry
> to route SQL22Server to the IP address. I was hoping I could just use the
> domain name.
> This creates an administrative overhead because we have to do add a host
> entry during the client install instead of having just assigning value to
the
> merge object.
> If I try the domain, the error I get is: The remote server does not exist
or
> has not been designated as a valid Publisher.
> I created the replication using the SQL22Server name.
> Thanks,
> Buzz
|||Thanks for the quick reply.
I am publishing what I found for the newsgroup.
For us, the publisher and the distributer are the same machine. We are using
FTP for the initial snapshot. We are using SQL Server 2000 SP4 on the server
and MSDE SP4 on the laptop subscribers.
I found I did not need the distributer values because my distributer and
publisher where the same machine. I will most likely set them anyway so that
someday in production I can have a different distributer.
Here are the subscriber properties of the Merge object:
.Distributor = "SQL22Server"
.DistributorSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.DistributorAddress = "company.com"
.DistributorNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.DistributorLogin = "login"
.DistributorPassword = "password"
.Publisher = "SQL22Server"
.PublisherAddress = "company.com"
.PublisherDatabase = "data"
.PublisherNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.Publication = "data"
.PublisherSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.PublisherLogin = "login"
.PublisherPassword = "password"
The one last thing to make sure is that when setting up the FTP on the
server, use the PublisherAddress value. So "company.com" so that the
subscriber hits ftp://company.com/.
Also if you do this in production be careful the change to the FTP address
causes the publication to force a recreation of the initial snapshot.
Thanks,
Buzz
"Hilary Cotter" wrote:

> use the activeX scripts to deploy your subscriptions. In it there are
> PublisherNetwork, DistributorNetwork, PublisherAddress, and
> DistributorAddress properties. These map to the entries you would otherwise
> put in your CNU or hosts file to make this work.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Buzz" <buzz@.online.nospam> wrote in message
> news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> to
> the
> or
>
>
|||Hi Buzz,
It looks more than a network issue.
- Could you PING SQL22Server from client and get the response?
- Could you telnet SQL22Server from client use the command like below
telnet <SQL22Server Domain Name>: 1433
- Do you have firewall between server and client? Have you open the TCP
port for them?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Replication Options

Hi, we have an SQL Server on Domain A that need to replicate to a client on
Domain B. There is no trust between the two domains. What are the options
we have to have a replication setup between the 2 SQL?
Thanks in advance for any answer!!
I forgot to mention but the main server is using Standard 2005 and client is
using Workgroup 2005
"Jas" wrote:

> Hi, we have an SQL Server on Domain A that need to replicate to a client on
> Domain B. There is no trust between the two domains. What are the options
> we have to have a replication setup between the 2 SQL?
> Thanks in advance for any answer!!
|||replicating between member servers in a work group is difficult as there is
a 5 or 10 connection limitation per machine.
basically you can use SQL authentication, and set your SQL Server agent
accounts up on both machines to run under an account which has the same name
and password on both the publisher and subscriber.
Then ensure this account has read and list files and folders rights on the
directory which underlies your snapshot share.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jas" <Jas@.discussions.microsoft.com> wrote in message
news:8DEC33DF-A653-43AD-A507-D0693FA031E6@.microsoft.com...
> Hi, we have an SQL Server on Domain A that need to replicate to a client
> on
> Domain B. There is no trust between the two domains. What are the
> options
> we have to have a replication setup between the 2 SQL?
> Thanks in advance for any answer!!
|||Is replication via FTP still working in 2005 version? Because it maybe a
solution...
"Hilary Cotter" wrote:

> replicating between member servers in a work group is difficult as there is
> a 5 or 10 connection limitation per machine.
> basically you can use SQL authentication, and set your SQL Server agent
> accounts up on both machines to run under an account which has the same name
> and password on both the publisher and subscriber.
> Then ensure this account has read and list files and folders rights on the
> directory which underlies your snapshot share.
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Jas" <Jas@.discussions.microsoft.com> wrote in message
> news:8DEC33DF-A653-43AD-A507-D0693FA031E6@.microsoft.com...
>
>
|||yes!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jas" <Jas@.discussions.microsoft.com> wrote in message
news:89544D88-6314-42CC-893E-D24D0B4789CE@.microsoft.com...[vbcol=seagreen]
> Is replication via FTP still working in 2005 version? Because it maybe a
> solution...
> "Hilary Cotter" wrote:
|||Is there any documentation on how to setup a replication using FTP in SQL
Server 2005?
"Hilary Cotter" wrote:

> yes!
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Jas" <Jas@.discussions.microsoft.com> wrote in message
> news:89544D88-6314-42CC-893E-D24D0B4789CE@.microsoft.com...
>
>

Replication only working 1 way

Hi Guys
I am running SQL2000 I have set up Transactional Replication with a push
subscription.
My 2 servers are not in the same domain but can see eachother.
Server 1 is Distributor as well as publisher. All insert, delete & updates
made on this side replicates fine to server 2, however any inserts, delete or
update made on server 2 does NOT replicate back to server 1.
I do not get any errors everything seems fine except for the lack of
replication.
Any ideas?
Thanks.
Regards
Jonas
Jonas,
Transactional replication is one way by default (Publisher -> Subscriber).
To get it bidirectional, you need to set up immediate updating subscriptions
or queued updating subscribers.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

replication is pending mode

hi guys,
Publication is in pending status. I don't know what is the problem.. I am using DOMAIN account(administrator). Publisher and subscriber are on same machine.
Error I got in my event viewer.
SQL Server Scheduled Job 'Replication agents checkup' (0xF2F0DE84FCFB1B46A009419F676E83A9) - Status: Failed - Invoked on: 2005-09-20 10:40:01 - Message: The job failed. Unable to determine if the owner (CORP\user) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'CORP\user'. [SQLSTATE 42000] (Error 8198)).
Kevin,
try changing the job owner to sa and then run the job.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||but it's under pending mode.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:e2KvrjfvFHA.3500@.TK2MSFTNGP09.phx.gbl...
Kevin,
try changing the job owner to sa and then run the job.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Kevin - I'm not too sure what's happening here - can't you change the job owner in SQL Server Agent, Jobs and then run it manually?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
|||now it's active.
Could you tell me what is difference between reinitialize subscription and synchronize? is that almost the same thing?
I'm assuming reinitialize subscription will refresh all the data,
and synchronize is just download the latest data.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:eXJhGhgvFHA.2076@.TK2MSFTNGP14.phx.gbl...
Kevin - I'm not too sure what's happening here - can't you change the job owner in SQL Server Agent, Jobs and then run it manually?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book: http://www.nwsu.com/0974973602p.html)
|||Kevin,
reinitialize will require that a new snapshot be generated and sent down to the subscriber as a set of odbcBCP files. On the other hand, synchronize will run the distribution/merge agent and send down the latest changes. For merge the flow of data is in both directions and is just pub -> sub for normal transactional replication. In the case of snapshot replication, synchronization and reinitialization are quite similar, but there's a big difference for the other methods.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Since it's in active mode, and I'm using transaction replication,
I did a test. I change column defintion for one of the column on publisher, and when I go to subscriber, how come I don't see the change? I also wait about 12 hours, it is still not there. Is it because it's depending on schedule? how do I force the synchronization?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:uMDS2PovFHA.2008@.TK2MSFTNGP10.phx.gbl...
Kevin,
reinitialize will require that a new snapshot be generated and sent down to the subscriber as a set of odbcBCP files. On the other hand, synchronize will run the distribution/merge agent and send down the latest changes. For merge the flow of data is in both directions and is just pub -> sub for normal transactional replication. In the case of snapshot replication, synchronization and reinitialization are quite similar, but there's a big difference for the other methods.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Kevin wrote on Wed, 21 Sep 2005 10:26:34 -0400:

> Since it's in active mode, and I'm using transaction replication,
> I did a test. I change column defintion for one of the column on
> publisher, and when I go to subscriber, how come I don't see the change?
> I also wait about 12 hours, it is still not there. Is it because it's
> depending on schedule? how do I force the synchronization?
Did you make the change using ALTER TABLE, or via the the
sp_repladdcolumn/sp_repldropcolumn procs or replication properties dialogs
in EM?. Check BOL for "Schema Changes on Publication Databases", according
to that ALTER TABLE changes to the schema are not replicated (I think I read
that SQL Server 2005 will be able to do this though).
Dan
|||YES. I changed it using alter table using following script. but I drop the article and then alter table, AND THEN I re-add article back in publication. SO even that method won't work?
altering the subscriptions
exec sp_dropsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
exec sp_droparticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
-- Change column definition
alter table tEmployees alter column Forename varchar(100) null
exec sp_addarticle @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.source_table = 'tEmployees'
exec sp_addsubscription @.publication = 'tTestFNames'
, @.article = 'tEmployees'
, @.subscriber = 'RSCOMPUTER'
, @.destination_db = 'testrep'
"Daniel Crichton" <msnews@.worldofspack.co.uk> wrote in message news:uYj2fPsvFHA.2132@.TK2MSFTNGP15.phx.gbl...
> Kevin wrote on Wed, 21 Sep 2005 10:26:34 -0400:
>
> Did you make the change using ALTER TABLE, or via the the
> sp_repladdcolumn/sp_repldropcolumn procs or replication properties dialogs
> in EM?. Check BOL for "Schema Changes on Publication Databases", according
> to that ALTER TABLE changes to the schema are not replicated (I think I read
> that SQL Server 2005 will be able to do this though).
> Dan
>
|||This is OK - if you're using transactional replication, you'll also need to run the snapshot then the distribution agents for it to go over. Also, Daniel's quite right that this type of tinkering is supported directly using the 'Replicate Schema Changes' option on the subscription options pane of SQL Server 2005 (by default is enabled).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

replication is in pending mode

hi guys,
I don't understand something, when I use domain account to do replication,
it's in pending mode for snapshot agent, but once I use sa account to do
replication, then it's in active mode. why can't I use domain account to
create replication?
The replication subsystem can't figure out if the domain account has rights
to start the service. A patch, not sure which one, broke this sometime ago.
I logon and register my servers in EM using the sa account and everything is
peachy.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kevin" <pearl_77@.hotmail.com> wrote in message
news:%23S%23iz20yFHA.596@.TK2MSFTNGP12.phx.gbl...
> hi guys,
> I don't understand something, when I use domain account to do
> replication, it's in pending mode for snapshot agent, but once I use sa
> account to do replication, then it's in active mode. why can't I use
> domain account to create replication?
>