push or pull, local or remote

sql2k sp3
Transactial, 1 way replication to 1 Subscriber. I want to offload as much
processing to the Subscriber as possible. I was thinking to use a Remote
Distributor (Subscriber) with Push Subscriptions would be good. (Push for
Security/ Firewall reasons.) Is this correct thinking?
TIA, ChrisR
I normally only migrate to a remote distributor when circumstances warrant.
For instance when my publisher is under load and I start to experience
locking especially in the distribution database.
There is an added point of failure if you move to a remote distributor when
you don't really need to.
Pull is best when you have large numbers of subscribers. You do lose the
central point of administration.
You might want to think about remote activation. This will offload your
agent processing to your subscriber. Its like a push subscription but with
less overhead on the publisher, and more on the subscriber.
For firewall issues you would use pull with FTP. Push doesn't work welll
over a firewall.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ChrisR" <chris@.noemail.com> wrote in message
news:uWARPlqoEHA.1992@.TK2MSFTNGP09.phx.gbl...
> sql2k sp3
> Transactial, 1 way replication to 1 Subscriber. I want to offload as much
> processing to the Subscriber as possible. I was thinking to use a Remote
> Distributor (Subscriber) with Push Subscriptions would be good. (Push for
> Security/ Firewall reasons.) Is this correct thinking?
> TIA, ChrisR
>
|||> You might want to think about remote activation. This will offload your
> agent processing to your subscriber. Its like a push subscription but with
> less overhead on the publisher, and more on the subscriber.
I had always thought this is what a Remote Distributor would do? Is this
incorrect? Also, Push/ Pull doesnt have anything to do with where the load
is placed, right?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23mFVPNvoEHA.516@.TK2MSFTNGP09.phx.gbl...
> I normally only migrate to a remote distributor when circumstances
warrant.
> For instance when my publisher is under load and I start to experience
> locking especially in the distribution database.
> There is an added point of failure if you move to a remote distributor
when[vbcol=seagreen]
> you don't really need to.
> Pull is best when you have large numbers of subscribers. You do lose the
> central point of administration.
> You might want to think about remote activation. This will offload your
> agent processing to your subscriber. Its like a push subscription but with
> less overhead on the publisher, and more on the subscriber.
> For firewall issues you would use pull with FTP. Push doesn't work welll
> over a firewall.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "ChrisR" <chris@.noemail.com> wrote in message
> news:uWARPlqoEHA.1992@.TK2MSFTNGP09.phx.gbl...
much[vbcol=seagreen]
for
>
|||No, a remote distributor contains all the commands to be replicated and the
history if you are using a push subscription.
If you are using a pull subscription your remote distributor only contains
all the commands to be replicated. This history is on the subscriber. If
your remote distributor is on your subscriber, and your pull subscription
agents are there as well then the commands and history are there.
With remote activiation your agent exe will run wherever you specify -
publisher, subcsriber or distributor. So you can run a pull subscription and
have the agent run on your publisher or a push subscription and have your
agent run on your publisher.
HTH
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ChrisR" <chris@.noemail.com> wrote in message
news:%234ZdwMxoEHA.3460@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
with[vbcol=seagreen]
>
> I had always thought this is what a Remote Distributor would do? Is this
> incorrect? Also, Push/ Pull doesnt have anything to do with where the load
> is placed, right?
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23mFVPNvoEHA.516@.TK2MSFTNGP09.phx.gbl...
> warrant.
> when
with[vbcol=seagreen]
> much
Remote
> for
>
|||So then whats the benifit to having a remote distributor. I always thought
if processing got really heavy on the Publisher I could just use a Remote
Distributor and that would fix it. It sounds like my whole thought process
is off?
My goals are:
To offload all the processing to the Subscriber. Keep as secure as possible.
After reading all this it sounds like I should:
Use a Local Distributor. Use Remote Activation Agent. Use Pull Subscriptions
with FTP.
Is this how you would do it for my scenario?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uQ4G7axoEHA.2340@.TK2MSFTNGP11.phx.gbl...
> No, a remote distributor contains all the commands to be replicated and
the
> history if you are using a push subscription.
> If you are using a pull subscription your remote distributor only contains
> all the commands to be replicated. This history is on the subscriber. If
> your remote distributor is on your subscriber, and your pull subscription
> agents are there as well then the commands and history are there.
> With remote activiation your agent exe will run wherever you specify -
> publisher, subcsriber or distributor. So you can run a pull subscription
and[vbcol=seagreen]
> have the agent run on your publisher or a push subscription and have your
> agent run on your publisher.
> HTH
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "ChrisR" <chris@.noemail.com> wrote in message
> news:%234ZdwMxoEHA.3460@.tk2msftngp13.phx.gbl...
your[vbcol=seagreen]
> with
load[vbcol=seagreen]
the[vbcol=seagreen]
your[vbcol=seagreen]
> with
welll[vbcol=seagreen]
> Remote
(Push
>
|||You are completely correct. To offload some of the processing involved in
replication use a remote distributor. The only replication overhead on the
publisher will be the log reader agent which will still run on the
publisher.
However, you will then have another point of failure. Life is simpler with a
local distributor.
When you migrate to pull you get better performance as the distribution
agent runs on the subscriber. But then you have to administer your
distribution agent on your subscriber, and consequently lose your single
central point of administration.
So its a trade off, administrative simplicity vs. the performance boost.
Same with remote activation; it is slightly more complex, but there can be
performance benefits by running your push agent on your subscriber - note
that is push agent, not pull. If the server you are running your
distribution agent on (publisher, subscriber, distributor) is under load you
may get dcom timeouts when you agent starts up.
If you chose the local distributor, and pull subscriptions with FTP you are
probably getting better performance than with local and push. You would get
better performance with remote and pull, but then there is the added
administrative burden - albeit slight.
If you want to throw remote activation into the mix where is your agent
going to run? Publisher, subscriber, distributor? For performance reasons
it should be the distributor or subscriber. If its the subscriber you should
be using a simple pull.
"ChrisR" <chris@.noemail.com> wrote in message
news:OaO7L0yoEHA.1712@.tk2msftngp13.phx.gbl...
> So then whats the benifit to having a remote distributor. I always thought
> if processing got really heavy on the Publisher I could just use a Remote
> Distributor and that would fix it. It sounds like my whole thought process
> is off?
> My goals are:
> To offload all the processing to the Subscriber. Keep as secure as
> possible.
> After reading all this it sounds like I should:
> Use a Local Distributor. Use Remote Activation Agent. Use Pull
> Subscriptions
> with FTP.
> Is this how you would do it for my scenario?
>
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uQ4G7axoEHA.2340@.TK2MSFTNGP11.phx.gbl...
> the
> and
> your
> load
> the
> your
> welll
> (Push
>
|||How would you do it? Publisher performance is more important to me than
centralized administration. It sounds like the ultimate performance boost
would be:
Remote Distributor. Pull Subscriptions. Remote Agent.
Would you agree?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OaeV0e1oEHA.3900@.TK2MSFTNGP10.phx.gbl...
> You are completely correct. To offload some of the processing involved in
> replication use a remote distributor. The only replication overhead on the
> publisher will be the log reader agent which will still run on the
> publisher.
> However, you will then have another point of failure. Life is simpler with
a
> local distributor.
> When you migrate to pull you get better performance as the distribution
> agent runs on the subscriber. But then you have to administer your
> distribution agent on your subscriber, and consequently lose your single
> central point of administration.
> So its a trade off, administrative simplicity vs. the performance boost.
> Same with remote activation; it is slightly more complex, but there can be
> performance benefits by running your push agent on your subscriber - note
> that is push agent, not pull. If the server you are running your
> distribution agent on (publisher, subscriber, distributor) is under load
you
> may get dcom timeouts when you agent starts up.
> If you chose the local distributor, and pull subscriptions with FTP you
are
> probably getting better performance than with local and push. You would
get
> better performance with remote and pull, but then there is the added
> administrative burden - albeit slight.
> If you want to throw remote activation into the mix where is your agent
> going to run? Publisher, subscriber, distributor? For performance reasons
> it should be the distributor or subscriber. If its the subscriber you
should[vbcol=seagreen]
> be using a simple pull.
>
> "ChrisR" <chris@.noemail.com> wrote in message
> news:OaO7L0yoEHA.1712@.tk2msftngp13.phx.gbl...
thought[vbcol=seagreen]
Remote[vbcol=seagreen]
process[vbcol=seagreen]
If[vbcol=seagreen]
subscription[vbcol=seagreen]
subscription[vbcol=seagreen]
your[vbcol=seagreen]
but[vbcol=seagreen]
lose[vbcol=seagreen]
but
>
|||I did some testing a couple of years ago with pulling from an FTP site.
Doesnt it have an issue with filling up the C: drive? Something like making
a copy of the snapshot in a temp folder?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OaeV0e1oEHA.3900@.TK2MSFTNGP10.phx.gbl...
> You are completely correct. To offload some of the processing involved in
> replication use a remote distributor. The only replication overhead on the
> publisher will be the log reader agent which will still run on the
> publisher.
> However, you will then have another point of failure. Life is simpler with
a
> local distributor.
> When you migrate to pull you get better performance as the distribution
> agent runs on the subscriber. But then you have to administer your
> distribution agent on your subscriber, and consequently lose your single
> central point of administration.
> So its a trade off, administrative simplicity vs. the performance boost.
> Same with remote activation; it is slightly more complex, but there can be
> performance benefits by running your push agent on your subscriber - note
> that is push agent, not pull. If the server you are running your
> distribution agent on (publisher, subscriber, distributor) is under load
you
> may get dcom timeouts when you agent starts up.
> If you chose the local distributor, and pull subscriptions with FTP you
are
> probably getting better performance than with local and push. You would
get
> better performance with remote and pull, but then there is the added
> administrative burden - albeit slight.
> If you want to throw remote activation into the mix where is your agent
> going to run? Publisher, subscriber, distributor? For performance reasons
> it should be the distributor or subscriber. If its the subscriber you
should[vbcol=seagreen]
> be using a simple pull.
>
> "ChrisR" <chris@.noemail.com> wrote in message
> news:OaO7L0yoEHA.1712@.tk2msftngp13.phx.gbl...
thought[vbcol=seagreen]
Remote[vbcol=seagreen]
process[vbcol=seagreen]
If[vbcol=seagreen]
subscription[vbcol=seagreen]
subscription[vbcol=seagreen]
your[vbcol=seagreen]
but[vbcol=seagreen]
lose[vbcol=seagreen]
but
>

Push data to remote server

Can I run bulk insert or bcp on a local server to insert data into a
remote server?
What are the other options to Push data to a remote server outside a
firewall?
Bulk insert is only for insert purposes -- you would need to run this on the
remote server. BCP does in/out. In theory you could run this from your
machine (with a file on your PC) and specify the remote server as the
destination.
You might be able to use replication or custom built insert statements that
utilize linked servers for connectivity.
Keith Kratochvil
"Rishi" <mrrishisharma@.gmail.com> wrote in message
news:1159992378.416088.171020@.b28g2000cwb.googlegr oups.com...
> Can I run bulk insert or bcp on a local server to insert data into a
> remote server?
> What are the other options to Push data to a remote server outside a
> firewall?
>

Push data to remote server

Can I run bulk insert or bcp on a local server to insert data into a
remote server?
What are the other options to Push data to a remote server outside a
firewall?Bulk insert is only for insert purposes -- you would need to run this on the
remote server. BCP does in/out. In theory you could run this from your
machine (with a file on your PC) and specify the remote server as the
destination.
You might be able to use replication or custom built insert statements that
utilize linked servers for connectivity.
Keith Kratochvil
"Rishi" <mrrishisharma@.gmail.com> wrote in message
news:1159992378.416088.171020@.b28g2000cwb.googlegroups.com...
> Can I run bulk insert or bcp on a local server to insert data into a
> remote server?
> What are the other options to Push data to a remote server outside a
> firewall?
>

Push data to remote server

Can I run bulk insert or bcp on a local server to insert data into a
remote server?
What are the other options to Push data to a remote server outside a
firewall?Bulk insert is only for insert purposes -- you would need to run this on the
remote server. BCP does in/out. In theory you could run this from your
machine (with a file on your PC) and specify the remote server as the
destination.
You might be able to use replication or custom built insert statements that
utilize linked servers for connectivity.
Keith Kratochvil
"Rishi" <mrrishisharma@.gmail.com> wrote in message
news:1159992378.416088.171020@.b28g2000cwb.googlegroups.com...
> Can I run bulk insert or bcp on a local server to insert data into a
> remote server?
> What are the other options to Push data to a remote server outside a
> firewall?
>

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonaldYou can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL
but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_
www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the d
b? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonald
You can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer (I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the db? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonaldYou can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL
but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_
www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the d
b? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Pulling stored Procs from a remote db

Hi all -
I am trying to rebuild a website abandoned by the builder and an SQLServer
(I think 2k) db is used under it at the host. I can get at the db by using
Access/ODBC with a URL but the migration facility seems only to let me get
at the tables.
There are about half a dozen SPs referred to in the ASP code ( eg EXEC
sp_www) and I want to get hold of the code as I am not sure at all what they
are doing.
How do I get the code for each SP and store it in the local copy of the db?
Can I just replicate the db and move the replica to a local area?
Any advice on this gratefully (!) receive
Thanks
Jim McDonald
You can get the source code of a stored procedure using sp_helptext.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jim McDonald" <jim@.missile.demon.co.uk> wrote in message
news:ct7q5g$n7j$1$8302bc10@.news.demon.co.uk...
> Hi all -
> I am trying to rebuild a website abandoned by the builder and an SQLServer (I think 2k) db is used
> under it at the host. I can get at the db by using Access/ODBC with a URL but the migration
> facility seems only to let me get at the tables.
> There are about half a dozen SPs referred to in the ASP code ( eg EXEC sp_www) and I want to get
> hold of the code as I am not sure at all what they are doing.
> How do I get the code for each SP and store it in the local copy of the db? Can I just replicate
> the db and move the replica to a local area?
> Any advice on this gratefully (!) receive
> Thanks
> Jim McDonald
>

Pull or push subscription?

Faustino,
I agree about pull, and you might also want to
investigate a remote distributor to offload production
server processing, especially if you are using
transactional replication.
HTH,
Paul Ibison
The problem with pull subscriptions is that you no longer have a central
point of administration.
What this means is that if a pull subscription agent fails you will not see
the error on your publisher, but will have to visit the subscriber to see
this error. To get around this use replication monitor group and add all the
subscribers to it.
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:3ec801c48ff9$11379320$a601280a@.phx.gbl...
> Faustino,
> I agree about pull, and you might also want to
> investigate a remote distributor to offload production
> server processing, especially if you are using
> transactional replication.
> HTH,
> Paul Ibison
|||Actually we are planning to do a merge replication with all sites. It is the
database for an order processing system. Each branch will be feeding us with
the orders and we will sent them price changes etc.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:3ec801c48ff9$11379320$a601280a@.phx.gbl...
> Faustino,
> I agree about pull, and you might also want to
> investigate a remote distributor to offload production
> server processing, especially if you are using
> transactional replication.
> HTH,
> Paul Ibison

Pull Merge constantly have all the same conflicts

Hello.

Let me describe first my replication setup:

- SQL Server 2005 SP1 (SP2 coming soon)

- Approximately 35 remote users (Salesrep laptop) using Pull Subscriptions

- Merge (Bi-Directional) (8 articles - tables only)

- Merge (Uni-Directional) (5 articles - tables only)

- Transactional (5 articles - tables only)

Users receive data based on their territory #, therefore they receive their customers sets of data. It happens that customer change from one territory to another but not frequently. When it happens, so far so good, the data is redirected to the new salesrep using the model we configured (Territory table with SUSER_NAME() to filter the data).

Ok, here's my problem. Since a while, I can see in the replication monitor that some users seems to log the same conflict again and again (Merge process). I mean, checking the history for many subscribers, there is always the same number in the "Conflict" colums.

As an example:

- Merge completed after processing 18 data change(s) (4 insert(s), 14 update(s), 0 delete(s), 31 conflict(s))

- Merge completed after processing 27 data change(s) (10 insert(s), 17 update(s), 0 delete(s), 31 conflict(s))

- Merge completed after processing 20 data change(s) (5 insert(s), 15 update(s), 0 delete(s), 31 conflict(s))

and so on...(Those are only 3 historical entries for a single subscriptions but there are many like that, always with the same count of conflict - vary per user). It appears to me that the same conflicts come over and over.

The thing is that if I decide to reinitialize a subscription, conflicts will disappear, therefore I know that it is not a process on the server that keeps changing the data; anyway, even if it was, changes would be applied on the subscription because the server always win in my setup.

Any idea what should I do with this? Any help would be greatly appreciated.

Thanks.

Can you use the conflict viewer to see what these conflicts are to see if they make sense to you?|||

Woops, I feel like an idiot now

Thanks for opening my mind!

Publishing to a remote SSL server

I've set up SQL Reports in 'https://www.projects.com/reports' and added a
reports project to a solution. I used the reports manager to add a folder in
which to deploy the reports, but can't figure out where it is on the server.
When I try to deploy a report to 'https://www.projects.com/reportserver' I
get the following error: 'A connection can not be made to the report server
https://www.projects.com/ReportServer'. Any help to do the following:
1. Set up a folder on the server to deploy the datasource and reports so I
can xcopy
2. Be able to make a connection when I attempt to deploy a report from
VS.NET.
Would be appreciated.
Thanks.
DanI resolved this problem by first installing the data source then the report.
The report runs on the local server, but any attempt to run the report or
sample reports over the internet gives the error: 'Cannot find server or DNS
Error'. I'm publishing behind ISA 2004. Any suggestions?
Thanks.
Dan
"Dan Slaby" <dls@.newsgroup.nospam> wrote in message
news:ucM%23rdOjFHA.3568@.tk2msftngp13.phx.gbl...
> I've set up SQL Reports in 'https://www.projects.com/reports' and added a
> reports project to a solution. I used the reports manager to add a folder
> in which to deploy the reports, but can't figure out where it is on the
> server. When I try to deploy a report to
> 'https://www.projects.com/reportserver' I get the following error: 'A
> connection can not be made to the report server
> https://www.projects.com/ReportServer'. Any help to do the following:
> 1. Set up a folder on the server to deploy the datasource and reports so I
> can xcopy
> 2. Be able to make a connection when I attempt to deploy a report from
> VS.NET.
> Would be appreciated.
> Thanks.
> Dan
>|||Hello,
I'd like to confirm that both report server and SQL server are behind ISA
2004.
Please note that Windows authentication is not supported via Internet
because Kerbose/NTLM authentication need open too many ports via firewall
which is not proper for security purpose.
If you want to run the report over the internet, you may need to enable
anonymous access. You need to configure via report manager to enable
Iusr_<computername> account to have the proper permission to the proper
roles such as browser/content manager etc.
I suggest that you perform the following steps to narrow down the issue:
1. Run the report internally from another client computer with anonymous
access.
If the user can run the report internally successfully with anonymous
access, you may need to check the configuration of the ISA server.
To enable Anonymous Access to work with SQL Server Reporting Services,
enable Anonymous Access under Directory Security in IIS and set the default
account to IWAM_machinename
NOTE: By default SQL Server Reporting Services uses the IWAM_machinename
account to connect.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.

Publisher cannot be droped becaused Remote Distributor down

Hi all,
I am having a problem now. I cannot drop my publisher and publication because i was uninstalled the remote distibutor before i disable al lthe publication. Now the remote distibutor no longer exist.
Can another one help me? Urgent!!I don't know of any way to remove replication using the GUI tools in the situation you've described, but it can be done fairly easily using Transact SQL stored procedure calls. Check out sp_droppublication (http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_repl2_617y.asp) and pay special attention to the @.ignore_distributor parameter. Microsoft normlly recommends that you use this only with the help of their PSS group, but your data may not be worth $750 to open a support incident with them, so you may choose to "go it alone" instead of calling them for help.

-PatP

publication include new tables created automatically?

Hi All,
I have a merge replication on a SQL 2000 database to a remote site.
I have selected "publish all" in publication properties. Now if I a new
table is created, does it automatically runs the snapshot agent and include
that table in to the table schema?
Thanks in advance for the answer... :-)
Maani...
Using sp_addmergearticle followed by running the snapshot agent and merge
agents should be enough.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .