putting subscriptions and other SSRS things in SourceSafe?

There are things configured/setup in Report Manager that we would like to
version in Visual SourceSafe... the setup of data-driven subscriptions, for
instance. Has anyone done this? Does anyone know of a third-party product
that assists with this?
I'm currently thinking of writing some code to take a
ReportServer.dbo.Subscriptions record and format it as an XML file that we
can put in VSS. Can anyone think up a better idea?You have to be careful with messing with rows of the database. We may
change the database at anytime and when you try and return it to the DB it
might not be the same anymore.
You could extract the information via the SOAP interface and then create a
script that would create the subscriptions. You could then save off these
scripts and use them against any RS server.
Also, is there a reason that backing up the DB is not good enough?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"FurmanGG" <FurmanGG@.discussions.microsoft.com> wrote in message
news:E05AB1EE-5671-4106-885D-627DDB28293A@.microsoft.com...
> There are things configured/setup in Report Manager that we would like to
> version in Visual SourceSafe... the setup of data-driven subscriptions,
> for
> instance. Has anyone done this? Does anyone know of a third-party product
> that assists with this?
> I'm currently thinking of writing some code to take a
> ReportServer.dbo.Subscriptions record and format it as an XML file that we
> can put in VSS. Can anyone think up a better idea?|||Daniel-
Sorry I wasn't clear. Our intention isn't to use the XML files that we
version in SourceSafe in order to ever restore or write anything back to the
database... it's just for versioning purposes... as in "what changed when we
deployed the Apr 12 release?" and doing a diff on the March and the April 12
file versions would tell us that. If we ever had to go back... or if anyone
accidentally deleted a report (which kills all its subscriptions)... we could
open up the XML and use it as a guide for reconstructing the recipients and
query of the data driven subscription... manually and through the Report
Manager interface.
So I take it nobody has any good suggestions for third-party software or
good processes for handling this? Does anyone else have similar needs?
"Daniel Reib (MSFT)" wrote:
> You have to be careful with messing with rows of the database. We may
> change the database at anytime and when you try and return it to the DB it
> might not be the same anymore.
> You could extract the information via the SOAP interface and then create a
> script that would create the subscriptions. You could then save off these
> scripts and use them against any RS server.
> Also, is there a reason that backing up the DB is not good enough?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "FurmanGG" <FurmanGG@.discussions.microsoft.com> wrote in message
> news:E05AB1EE-5671-4106-885D-627DDB28293A@.microsoft.com...
> > There are things configured/setup in Report Manager that we would like to
> > version in Visual SourceSafe... the setup of data-driven subscriptions,
> > for
> > instance. Has anyone done this? Does anyone know of a third-party product
> > that assists with this?
> >
> > I'm currently thinking of writing some code to take a
> > ReportServer.dbo.Subscriptions record and format it as an XML file that we
> > can put in VSS. Can anyone think up a better idea?
>
>

Put data on Windows Storage 2003

We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
Would it be possible to setup an SQL-server on another Windows 2003 server
but ...
put the data on the NAS-server?
And if so what could be the disadvantages?No, you can only use local storage for SQL Server (with local I include SAN, as it is viewed by the
OS as being local). Well, there used to be a trace flag you could add to be able to create a
database on a remote server, but the general consensus is to *not* use it and I don't know it that
even still exists.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in message
news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?|||try to use the iSCSI protocol.
you can install an iSCSI target (server) on you storage server and connect
your SQL server to this iSCSI server.
the performance is better then a shared folder access.
but limited by the network speed.
for iSCSI I recommand to setup a dedicated subnet with Gbps cards and
switches that support jumbo frames.
Some Storage server vendors provides an iSCSI target in option.
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in
message news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?

Put data on Windows Storage 2003

We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
Would it be possible to setup an SQL-server on another Windows 2003 server
but ...
put the data on the NAS-server?
And if so what could be the disadvantages?No, you can only use local storage for SQL Server (with local I include SAN,
as it is viewed by the
OS as being local). Well, there used to be a trace flag you could add to be
able to create a
database on a remote server, but the general consensus is to *not* use it an
d I don't know it that
even still exists.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in mes
sage
news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?|||try to use the iSCSI protocol.
you can install an iSCSI target (server) on you storage server and connect
your SQL server to this iSCSI server.
the performance is better then a shared folder access.
but limited by the network speed.
for iSCSI I recommand to setup a dedicated subnet with Gbps cards and
switches that support jumbo frames.
Some Storage server vendors provides an iSCSI target in option.
"MarioFromBelgium" <MarioFromBelgium@.discussions.microsoft.com> wrote in
message news:73F03CB4-87F8-4221-85FF-91AF6539B7F7@.microsoft.com...
> We have a NAS-server with WIndows storage 2003, with 3 data-disks in Raid.
> Would it be possible to setup an SQL-server on another Windows 2003 server
> but ...
> put the data on the NAS-server?
> And if so what could be the disadvantages?

Push Subscription Wizard

Hello,
I am trying to setup a push subscription between two SQL 2000 Servers using
the Push Subscription Wizard through Enterprise Manager. After clicking
"Finish" at the end of the wizard, Enterprise Manager hangs at the first
step "Enabling this server as a subscriber". Can anyone help me identify
the problem, I can't see anything in the logs.
Thanks,
Ben Gibson
Ben,
additionally, you could use sp_who2 and dbcc inputbuffer(spid) as per usual
to get some more info.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

push snapshot

Hi I'm trying to setup a push replication between 2 servers on different
networks. both machines can ping eachother using there machine names. I setup
the publication and the distributor on the push server and generate a
snapshot. I then run the distributor but it fails to connect to the
subscriber.
thanks for the help.
Mark
You need to ensure the @.@.servername of the subscriber is how the
publisher/distributor refer to it and vice versa. If you have to use IP
address, you can setup client side alias on the distributor that maps the IP
address to the @.@.servername of the subscriber
“This posting is provided "AS IS" with no warranties, and confers no rights.”
"ACDMark" wrote:

> Hi I'm trying to setup a push replication between 2 servers on different
> networks. both machines can ping eachother using there machine names. I setup
> the publication and the distributor on the push server and generate a
> snapshot. I then run the distributor but it fails to connect to the
> subscriber.
> thanks for the help.
> Mark
|||hi ,
be sure that your sql agent services is
running on a domain account
that has permission to your snapshot folder
and the database
thanks,
joey
"ACDMark" wrote:

> Hi I'm trying to setup a push replication between 2 servers on different
> networks. both machines can ping eachother using there machine names. I setup
> the publication and the distributor on the push server and generate a
> snapshot. I then run the distributor but it fails to connect to the
> subscriber.
> thanks for the help.
> Mark

Push or Pull for Replication-Based failover

I am trying to devise a setup where I can use Replication to maintain a
failover server in case of a critical failure on the primary DB server. I
plan on using transactional replication and immeadiate updating for minimal
latency, but I have a couple of questions about the right setup:
1. Push or pull? Push would allow for 2 phase commit, which seems
desirable. On the other hand, when system 1 fails, don't you need to "break
the link" between the subscriber and publisher (i.e. run sp_dropsubscription)
in order to ensure proper operation?
2. We have some identity columns. I am planning on marking them as NOT FOR
REPLICATION and then in a failover scenario, run DBCC CHECKIDENT('my
table',RESEED,<looked up max from table>) to reseed the identity on the
secondary. Is this an advisable strategy?
I have been looking at other solutions in this area which involve modifying
some of the generated procs and I would like to avoid that so that we can use
as much out of the box as possible (trying not to pretend I can engineer
better than MS ).
Thanks,
Tom
Push or pull doesn't really relate to 2PC - the setting really controls who
initiates the distributor->subscriber traffic. If the subscriber fails, the
2PC won't matter because it is in the direction subscriber->distributor. The
other way round and you'll have to remove the subscription.
For the identities, the easiest solution is to set up immediateupdating with
queued updating failover and have a large seed set up.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Could you clarify a bit? does subscriber->distributor imply pull whereas
distributor ->subscriber implies push? I am trying to understand when I
would have to remove the subscription.
Thanks,
Tom
"Paul Ibison" wrote:

> Push or pull doesn't really relate to 2PC - the setting really controls who
> initiates the distributor->subscriber traffic. If the subscriber fails, the
> 2PC won't matter because it is in the direction subscriber->distributor. The
> other way round and you'll have to remove the subscription.
> For the identities, the easiest solution is to set up immediateupdating with
> queued updating failover and have a large seed set up.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||The directions I indicated refer to data flow, eg subscriber->distributor in
your case is 2PC, whereas distributor ->subscriber is the PUSH/PULL running
of the distribution agent. I think you're mixing PUSH/PULL with the flow of
data, while the 2 are not really related in that way - it's more which
computer is going to do the synchronization work.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

purge all history from msdb

I am looking for a way to setup a periodic delete from all history tables in
msdb, to prevent excessive growth. I am wondering if the following procedures
includes all necessary deletes.
1) In the maintenance plan wizard reporting tab, setting the number of
records to retain in sys_dbmaintplanhistory; older records will be deleted.
2) Run sp_delete_backuphistory to delete records from several backup and
restore history tables.
3) Run sp_purge_jobhistory to remove history from other jobs.
Am I missing anything? There is also an sp_purgehistory, but BOL says this
is for backward compatibility only; does anyone use this?
--
MunchingBillHi Munching,
Thanks for your post.
It is not necessary for you to execute sp_purgehistory. Based on my
knowledge, these three steps you have listed are sufficient for you to
delete from all history tables.
Also, please note that this question appears to be consulting in nature. We
would also like to introduce you to the CSS Advisory Services team.
Advisory Services is a remotely delivered, hourly fee-based, consultative
support option that provides a comprehensive result beyond your break-fix
product maintenance needs. It is an hourly fee-based, consultative
support option that provides proactive support beyond your break-fix
product maintenance needs. This support option includes working with the
same technician for assistance with issues like product migration, code
review, or new program development.
For more info in the US and Canada:
http://support.microsoft.com/default.aspx?pr=AdvisoryService
Outside of the US/Canada:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx
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.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

purge all history from msdb

I am looking for a way to setup a periodic delete from all history tables in
msdb, to prevent excessive growth. I am wondering if the following procedure
s
includes all necessary deletes.
1) In the maintenance plan wizard reporting tab, setting the number of
records to retain in sys_dbmaintplanhistory; older records will be deleted.
2) Run sp_delete_backuphistory to delete records from several backup and
restore history tables.
3) Run sp_purge_jobhistory to remove history from other jobs.
Am I missing anything? There is also an sp_purgehistory, but BOL says this
is for backward compatibility only; does anyone use this?
--
MunchingBillHi Munching,
Thanks for your post.
It is not necessary for you to execute sp_purgehistory. Based on my
knowledge, these three steps you have listed are sufficient for you to
delete from all history tables.
Also, please note that this question appears to be consulting in nature. We
would also like to introduce you to the CSS Advisory Services team.
Advisory Services is a remotely delivered, hourly fee-based, consultative
support option that provides a comprehensive result beyond your break-fix
product maintenance needs. It is an hourly fee-based, consultative
support option that provides proactive support beyond your break-fix
product maintenance needs. This support option includes working with the
same technician for assistance with issues like product migration, code
review, or new program development.
For more info in the US and Canada:
http://support.microsoft.com/defaul...AdvisoryService
Outside of the US/Canada:
http://support.microsoft.com/defaul...ernational.aspx
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.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

purge all history from msdb

I am looking for a way to setup a periodic delete from all history tables in
msdb, to prevent excessive growth. I am wondering if the following procedures
includes all necessary deletes.
1) In the maintenance plan wizard reporting tab, setting the number of
records to retain in sys_dbmaintplanhistory; older records will be deleted.
2) Run sp_delete_backuphistory to delete records from several backup and
restore history tables.
3) Run sp_purge_jobhistory to remove history from other jobs.
Am I missing anything? There is also an sp_purgehistory, but BOL says this
is for backward compatibility only; does anyone use this?
MunchingBill
Hi Munching,
Thanks for your post.
It is not necessary for you to execute sp_purgehistory. Based on my
knowledge, these three steps you have listed are sufficient for you to
delete from all history tables.
Also, please note that this question appears to be consulting in nature. We
would also like to introduce you to the CSS Advisory Services team.
Advisory Services is a remotely delivered, hourly fee-based, consultative
support option that provides a comprehensive result beyond your break-fix
product maintenance needs. It is an hourly fee-based, consultative
support option that provides proactive support beyond your break-fix
product maintenance needs. This support option includes working with the
same technician for assistance with issues like product migration, code
review, or new program development.
For more info in the US and Canada:
http://support.microsoft.com/default...dvisoryService
Outside of the US/Canada:
http://support.microsoft.com/default...rnational.aspx
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.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Pull Subscription for transactional replication

I have setup a pull subscription on the subscriber for transactional replication. The distribution job continues to run, but doesn't do anything because it says: The initial snapshot for publication 'man4' is not yet available.

How can I tell if the snapshot is running, and can I see the snapshot where it was created?The snapshot is set up on the publisher and must be created before any subscriptions are set up.

pull subscription - anynonomous - error HELP

I can't get an anynonmous pull subscription to work. Server is Windows
2000 with SQL Server 2000, client is XP Pro with MSDE 2000.
Setup replication on the server using the wizard:
Snapshot folder in default location
merge one database
don't select any subscribers (my client isn't listed)
Create publication using wizard
Merge
select one table
allow anonymous is marked
After the publication is created, go into the properties of the
publication:
Change the snapshot location to c:\inetpub\ftproot
set the FTP user/login (this login has admin rights)
Run the snapshot agent and the snapshot created successfully.
Now, on the client. the database tables exist, but there is no data.
Select Pull-Subscription to laptop / Pull New Subscription
Specify publication info
Connect using SQL Server authentication, enter login/password (has admin
and SA rights)
agent - use SQL server, same login/password
select database
Yes, initialize the schema and data
download the snapshot using FTP
on demand only
On the client, goto pull subscription under database in EM,
select start synchrnizing.
Server and Client receive error:
The schema script "\\iis-sql\C$\program file\microsoft sql
server\mssql\reldata\unc\iis-sql_msilex_msilex\20051215081206\ARCustomer
_1.sch could not be propaged to the subscriber.
Why do I get this message. I told it to use FTP so why/what is trying to
use the default repl directory.
I need to get this working like this, and then I will work on SQLDMO.
Thanks in advance.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Did you configure your pull subscription to download the snapshot using ftp?
It doesn't look like it.
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
"Darin" <darin_nospam@.nospamever> wrote in message
news:%23vkgNpYAGHA.3268@.TK2MSFTNGP10.phx.gbl...
>I can't get an anynonmous pull subscription to work. Server is Windows
> 2000 with SQL Server 2000, client is XP Pro with MSDE 2000.
> Setup replication on the server using the wizard:
> Snapshot folder in default location
> merge one database
> don't select any subscribers (my client isn't listed)
> Create publication using wizard
> Merge
> select one table
> allow anonymous is marked
> After the publication is created, go into the properties of the
> publication:
> Change the snapshot location to c:\inetpub\ftproot
> set the FTP user/login (this login has admin rights)
> Run the snapshot agent and the snapshot created successfully.
> Now, on the client. the database tables exist, but there is no data.
> Select Pull-Subscription to laptop / Pull New Subscription
> Specify publication info
> Connect using SQL Server authentication, enter login/password (has admin
> and SA rights)
> agent - use SQL server, same login/password
> select database
> Yes, initialize the schema and data
> download the snapshot using FTP
> on demand only
> On the client, goto pull subscription under database in EM,
> select start synchrnizing.
> Server and Client receive error:
> The schema script "\\iis-sql\C$\program file\microsoft sql
> server\mssql\reldata\unc\iis-sql_msilex_msilex\20051215081206\ARCustomer
> _1.sch could not be propaged to the subscriber.
> Why do I get this message. I told it to use FTP so why/what is trying to
> use the default repl directory.
> I need to get this working like this, and then I will work on SQLDMO.
> Thanks in advance.
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
|||yes, I did. But, even if I re-do everything to NOT use FTP I get the
exact same error.
Did my steps on the wizards seem correct? Did I miss something that has
to be done outside the wizards?
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||I got it to work FINALLY.
I am not using FTP (I didn't want to anyway, just thought I would try).
The problem was the client server agent account was set to use local
system. I changed that to the same login/password as everything else
(had to create a new user and give admin rights to) and it successfully
replicated.
Now to work on getting it to work from SQLDMO.
Darin
*** Sent via Developersdex http://www.codecomments.com ***

Pull replication setup problem

Hi,
I am changing the scenario of our replication from Push to Pull, but I could
not set up the Pull replication.
The publisher and distributor are on the same machine.
The subscriber always gets an error message as
"The process could not read file
"E:\repl\unc\MyServer_MyDB\200508\tableone.sch " due to OS error 3.
I searched a lot on the google, but no one seems fit my problem.
I am using SQL Server 2000 on both the Publisher and Subscriber.
Thanks for any help
Frank
Frank,
can you log on to the subscriber using the sql server agent's login and see
if you can read the snapshot share?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Pull Replication Idle Time

Hello,
i set up an pull replication. The first client i setup replication over
LAN and the second client i setup replication over RAS.
Server:
Windows Server 2003
SQL Server 2000
Client PCs:
Windows XP
Pull Replication over MS Syncmanager on demand
Now my problem:
At the first client (setup by LAN) the replication works fine over LAN.
When the client goes outside the office and start the replication over
RAS: It tooks a long time (up to 60 min) to start the replication
process. Sometimes the replication not even starts.
In the syncmanager it looks like the replication hangs.
When the client comes back in the office. The replication works fine?
At the second client (replication setup by RAS) the replication works
fine over RAS.
When the client comes back into the office and start the replication
over LAN: It takes a long time (up to 60 min) to start the replication
process. Sometimes the replication not even starts.
In the syncmanager it looks like the replication hangs.
When the client replicate over RAS. The replication works fine?
The name resolution in my network works good! Is there an cache in the
SQL Server or somebody knows an solution?
Best regards
Tulio Mossoro
looks like a bandwidth problem. Run profiler and see where it is getting
stuck. Also copy a 1 mg file across the RAS link and compare how long this
takes with when you copy it locally.
You can also get an idea of relative bandwidth via ras and compare it with
relative bandwidth via LAN by doing speed tests at
http://www.bandwidth.com/tools/speedTest
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
"Tulio" <mossorous@.yahoo.de> wrote in message
news:1128676983.748349.239970@.z14g2000cwz.googlegr oups.com...
> Hello,
> i set up an pull replication. The first client i setup replication over
> LAN and the second client i setup replication over RAS.
> Server:
> Windows Server 2003
> SQL Server 2000
> Client PCs:
> Windows XP
> Pull Replication over MS Syncmanager on demand
>
> Now my problem:
> At the first client (setup by LAN) the replication works fine over LAN.
> When the client goes outside the office and start the replication over
> RAS: It tooks a long time (up to 60 min) to start the replication
> process. Sometimes the replication not even starts.
> In the syncmanager it looks like the replication hangs.
> When the client comes back in the office. The replication works fine?
> At the second client (replication setup by RAS) the replication works
> fine over RAS.
> When the client comes back into the office and start the replication
> over LAN: It takes a long time (up to 60 min) to start the replication
> process. Sometimes the replication not even starts.
> In the syncmanager it looks like the replication hangs.
> When the client replicate over RAS. The replication works fine?
> The name resolution in my network works good! Is there an cache in the
> SQL Server or somebody knows an solution?
> Best regards
> Tulio Mossoro
>
|||Hello Hilary,
thanks for your fast answer but this can not be an bandwith problem.
On a few clients it is slow over RAS, on other clients it is slow over
LAN, on other clients it work perfect.
When i set up the replication via RAS then it is slow over LAN. Over RAS
it works perfect.
When i set up replication over LAN it is slow over RAS. Over LAN it
works perfect.
And the best at the end: The first two or three times it works perfect
in any direction. After this the replication gets slow up to not
working.
Is there any SQL Cache that holds the IP?
Thanks a lot in advance
Tulio Mossorous
*** Sent via Developersdex http://www.codecomments.com ***

Pull replication errors...

Hi,
the idea is to setup an offsite backup of our single sql server, have
created a publication on the MASTER server, and pulled it to the offsite
server using FTP, downloaded snapshot, replicated transactions, all appeared
to work, generated schema, but the frontend database app didnt run, loads of
various errors showing up.
decided to restore the database from disk to the backup server, to check the
app is working fine, which it now is, so all i need to do is replicated the
changes in the tables on the master server to the offsite server, only needs
to be one-way, the offsite is only for backup read only...changed the
publication to tables only, re-created snapshot and now get errors saying...
Cannot update identity column. The step failed
help please on solution or other ways to achive this.
comment the identity column update in the update proc.
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
"Matt" <mattnj@.hotmail.com> wrote in message
news:d9tqpf$gkn$1@.news.freedom2surf.net...
> Hi,
> the idea is to setup an offsite backup of our single sql server, have
> created a publication on the MASTER server, and pulled it to the offsite
> server using FTP, downloaded snapshot, replicated transactions, all
> appeared to work, generated schema, but the frontend database app didnt
> run, loads of various errors showing up.
> decided to restore the database from disk to the backup server, to check
> the app is working fine, which it now is, so all i need to do is
> replicated the changes in the tables on the master server to the offsite
> server, only needs to be one-way, the offsite is only for backup read
> only...changed the publication to tables only, re-created snapshot and
> now get errors saying...
> Cannot update identity column. The step failed
> help please on solution or other ways to achive this.
>

Pull Merge replication between two SQL Server machines in different, but trusted domains

Hi,
We are attempting to setup Pull Merge replication between two SQL Server
(SQL 2K sp3a, Windows Authentication) machines in different domains. We have
been able to get Pull Merge replication to work within the same domain.
While we are running Win2k on both machines, two one way trusts were setup
between them. The server are linked to each other, but cannot initiate the
replication agents. The message we get is:
SQL Server Agent could not access the replication agent. Use the DCOMCNFG
utility to confirm that the SQL Server Agent Windows account has permissions
to launch the replication agent. The step failed.
I did not spot any in DCOMCNFG, but I am not familiar with it. Any
suggections?
Tia
Paul
Paul,
here is an MSDN article which shows how to enable the merge agent to be run
remotely:
http://msdn.microsoft.com/library/de...us/howtosql/ht
_replctem_6c1l.asp
HTH,
Paul Ibison
|||I have a feeling that the error message may be misleading me away from the
true problem. It appears that DCOMCNFG is used for running agents remotely.
I am looking at having the push replication run at the distributor and pull
replications to run at the subscriber. Besides, I couldn't get it to work by
using DCOMCNFG.
I want to have one merge publication which is pushed to subscribers which
will not be intentionally disconnected from the network. And, the same
publication pulled to subscribers which will be removed from the network for
possibly weeks. This currently works as long as long as all the servers are
in the same domain. The problem is that the pull subscribers will be in
different domains with trust relationship setup between them and the
distributor.
When I take the existing scripts that work when all of the server are in the
same domain and run them with the pull subscriber in different domains I get
the error:
SQL Server Agent could not access the replication agent. Use the DCOMCNFG
utility to confirm that the SQL Server Agent Windows account has permissions
to launch the replication agent. The step failed.
I don't think this has any thing to do with running the agent remotely, but
I'm not sure. Any suggestions?
Thanks
Paul
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uQmkhv7FEHA.744@.TK2MSFTNGP09.phx.gbl...
> Paul,
> here is an MSDN article which shows how to enable the merge agent to be
run
> remotely:
>
http://msdn.microsoft.com/library/de...us/howtosql/ht
> _replctem_6c1l.asp
> HTH,
> Paul Ibison
>
|||PaulW,
The easiest way to set up replication between different domains is to create a local user account on both the servers with the same username and password. Make the account an administrator of the local machine. Then set this account as the startup account
for the SQL Server Agent. Restart the SQL Server agent and start the merge agent. This should fix your problem.
Regards
Chris R
|||Thanks for the response. I saw that option for non-trusted domains and when
I presented it, the option was quickly shot down because the production
system will be administered by different companies and they didn't want to
be forced to share passwords..
Thanks,
Paul
"Chris R" <crichardson@.iir-central.com> wrote in message
news:7CE505D6-BE9C-40E4-80D4-75F7287AAB3C@.microsoft.com...
> PaulW,
> The easiest way to set up replication between different domains is to
create a local user account on both the servers with the same username and
password. Make the account an administrator of the local machine. Then set
this account as the startup account for the SQL Server Agent. Restart the
SQL Server agent and start the merge agent. This should fix your problem.
> Regards
> Chris R
|||Non-trusted domains can also be set up using the Guest account, but I would assume that this is even less likely to be allowed :-)
Regards,
Paul Ibison
|||I already know that the guest account has been disabled. There will be a two
way trust between the domains. I don't know how that got approved. There
must be some way to perform pull subscriptions in a trusted relationship
without matching accounts and passwords.
Paul
|||Paul,
I have used pass-through security, or the guest account, because of working
in a non-trusted environment but in your case you should be able to use
impersonation. Have a look at this article:
http://support.microsoft.com/?id=321822.
Regards,
Paul Ibison
|||I think I got it. We started having net work troubles once it appeared to be
working, so I'm not sure. The problem was that the SQL Server agent accounts
had the same name on both machines, but different passwords. Once I changed
the name of the account on one machine and gave it dbo access to the other
machine's database it looked like it was working. Most of the initial
snapshot was applied, but it failed due to the retry count. Before this
change, it never get started.
Thanks for the help.
Paul

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!

Pull from the DMZ?

Ok, so in my scenario, if I have a one way trust & am already replicating to the DMZ, I should be able to setup a publication on the DMZ & pull, right?
Yes, I have done this. I think you will need to make the publication on the
server in the DMZ anonymous, so you don't have to register the subscriber on
the DMZ Publisher.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:%237vu$Du7FHA.1032@.TK2MSFTNGP11.phx.gbl...
Ok, so in my scenario, if I have a one way trust & am already replicating to
the DMZ, I should be able to setup a publication on the DMZ & pull, right?
|||Oh thanx for adding the bit about making the DMZ publication anonymous, you may have actually saved the last strand of hair on my head from being ripped out!!!!
Jude
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:%23NQwMFu7FHA.2040@.TK2MSFTNGP14.phx.gbl...
Yes, I have done this. I think you will need to make the publication on the
server in the DMZ anonymous, so you don't have to register the subscriber on
the DMZ Publisher.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:%237vu$Du7FHA.1032@.TK2MSFTNGP11.phx.gbl...
Ok, so in my scenario, if I have a one way trust & am already replicating to
the DMZ, I should be able to setup a publication on the DMZ & pull, right?

Publisher migration

Hi,
I have a Merge replication setup to replicate from server A (Florida) to
server B (Spain).
We bought a new server and want to replace server A by server N in Florida.
Is there a guideline on how to do this? (appart from the
"starting-from-scratch" approach).
Also, i would like to do it little by little; first I want to have N to be a
subscriber of A; eventually I would like to change it to be the publisher.
Thanks for your help... Jos Araujo.
Jos,
I cannot say how to do it little by little, from what I know it is boring
and painful. If you want to do it at once - it is quite simple, I did it and
it worked just fine. Just make two servers with similar directory structure,
copy database files to a second server, give it the name of the first server
and you're done. Here are the details:
1. Install SQL Server on the server N, with all the upgrades that you have
on the server A, so that the versions of SQL Servers on both computers are
exactly the same.
2. Make sure the default data files directory as well as startup parameters
on both servers are exactly the same. (Enterprise Manager - SQL Server
Properties - General tab - Startup Parameters, and Database Settings tab -
Default Data directory).
3. Stop SQL Servers on both computers A and N. Just in case you can save
files from the database folder on N - move them to another folder. Now copy
all the files from server A database folder to the corresponding folder on
the server N.
4. Disconnect both computers A and N from the network
5. Rename computer N to match computer A, reboot and make sure all the
databases are online. At this point if something goes wrong and you need
your server running right away, you can simply reconnect server A to the
network and start SQL Server there; in this case you will later have to
continue from step 2. Obviously, now you cannot have both computers running
on the same network, because they have the same name. Of course, you can
rename A too.
6. Replace A with N on the network, now you are ready to go. Hopefully
everything will work fine...
To play it safe you can try it first in your local environment, and also you
can disable all but one test subscription, replace the server, make sure
your test subscription can synchronize, and finally enable all the remaining
subscriptions. Personally, I think that the second suggestion is an
overkill, but it's your decision.
Good luck,
Igor
"Jose Araujo" <josea@.mcrinc.com> wrote in message
news:uF75UWEEFHA.3244@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have a Merge replication setup to replicate from server A (Florida) to
> server B (Spain).
> We bought a new server and want to replace server A by server N in
> Florida.
> Is there a guideline on how to do this? (appart from the
> "starting-from-scratch" approach).
> Also, i would like to do it little by little; first I want to have N to be
> a
> subscriber of A; eventually I would like to change it to be the publisher.
> Thanks for your help... Jos Araujo.
>
|||Thanks a lot!
Jos.
"Igor Rass" <irass{nospam}@.optonline.net> wrote in message
news:OmXuuy4EFHA.3416@.TK2MSFTNGP09.phx.gbl...
> Jos,
> I cannot say how to do it little by little, from what I know it is boring
> and painful. If you want to do it at once - it is quite simple, I did it
and
> it worked just fine. Just make two servers with similar directory
structure,
> copy database files to a second server, give it the name of the first
server
> and you're done. Here are the details:
> 1. Install SQL Server on the server N, with all the upgrades that you have
> on the server A, so that the versions of SQL Servers on both computers are
> exactly the same.
> 2. Make sure the default data files directory as well as startup
parameters
> on both servers are exactly the same. (Enterprise Manager - SQL Server
> Properties - General tab - Startup Parameters, and Database Settings tab -
> Default Data directory).
> 3. Stop SQL Servers on both computers A and N. Just in case you can save
> files from the database folder on N - move them to another folder. Now
copy
> all the files from server A database folder to the corresponding folder on
> the server N.
> 4. Disconnect both computers A and N from the network
> 5. Rename computer N to match computer A, reboot and make sure all the
> databases are online. At this point if something goes wrong and you need
> your server running right away, you can simply reconnect server A to the
> network and start SQL Server there; in this case you will later have to
> continue from step 2. Obviously, now you cannot have both computers
running
> on the same network, because they have the same name. Of course, you can
> rename A too.
> 6. Replace A with N on the network, now you are ready to go. Hopefully
> everything will work fine...
> To play it safe you can try it first in your local environment, and also
you
> can disable all but one test subscription, replace the server, make sure
> your test subscription can synchronize, and finally enable all the
remaining[vbcol=seagreen]
> subscriptions. Personally, I think that the second suggestion is an
> overkill, but it's your decision.
> Good luck,
> Igor
> "Jose Araujo" <josea@.mcrinc.com> wrote in message
> news:uF75UWEEFHA.3244@.TK2MSFTNGP15.phx.gbl...
be[vbcol=seagreen]
publisher.
>

Publish scenario - how can this work?

Our current setup has a hand held device, a laptop and head office. The
field reps have the hand held and laptop and need to get and send data back
to head office. Merge Replication seems to be the answer and I was thinking
that the Head Office would publish to the Laptop and the Laptop would then
publish to the Hand Held. But SQL Server 2005 Express can only be a
Subscriber and not a Publisher.
The reason to do this is that only certain rows will be published to the
laptop (say 1 weeks work) and then only certain rows (say 1 or 2 days work)
will be published to the hand held.
Is there a way to accomplish this?
Here's how it breaks down:
Head Office = SQL Server 2005 Standard Edition
Laptop = SQL Server 2005 Express Edition
Hand Held = SQL Server 2005 Compact Edition
Thanks,
Richard.
You might want to look at RDA as the transit mechanism between Express and
the HandHelds.
Otherwise I would replicate from the Standard Edition publisher to the
handhelds.
http://www.zetainteractive.com - Shift Happens!
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
"Richard Wodabek" <rwodabek@.cogeco.ca> wrote in message
news:uocMysrNIHA.2268@.TK2MSFTNGP02.phx.gbl...
> Our current setup has a hand held device, a laptop and head office. The
> field reps have the hand held and laptop and need to get and send data
> back
> to head office. Merge Replication seems to be the answer and I was
> thinking
> that the Head Office would publish to the Laptop and the Laptop would then
> publish to the Hand Held. But SQL Server 2005 Express can only be a
> Subscriber and not a Publisher.
> The reason to do this is that only certain rows will be published to the
> laptop (say 1 weeks work) and then only certain rows (say 1 or 2 days
> work)
> will be published to the hand held.
> Is there a way to accomplish this?
> Here's how it breaks down:
> Head Office = SQL Server 2005 Standard Edition
> Laptop = SQL Server 2005 Express Edition
> Hand Held = SQL Server 2005 Compact Edition
> Thanks,
> Richard.
>
|||Thanks Hilary, RDA might work for us.
Any chance 2008 Express Edition will allow Publishing?
Richard.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uNmcUmzNIHA.292@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> You might want to look at RDA as the transit mechanism between Express and
> the HandHelds.
> Otherwise I would replicate from the Standard Edition publisher to the
> handhelds.
> --
> http://www.zetainteractive.com - Shift Happens!
> 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
> "Richard Wodabek" <rwodabek@.cogeco.ca> wrote in message
> news:uocMysrNIHA.2268@.TK2MSFTNGP02.phx.gbl...
then
>

Publication has expired

I have setup transaction replication using seperate server for distribution
box.
Server A - Publisher (Win2003, SQL2000 SP818)
Server B - Distributor (Win2003, SQL2000 SP818)
Server C - Subscriber1 (Win2003 and SQL2000 SP818)
Server D - Subscriber2 (Win2003 and SQL2000 SP818)
Server E - Subscriber3 (Win2000, SQL2000 SP818)
Server A has 3 publishers and each publisher has more than 10 articles, one
of them we use it for monitoring replication by update a datetime column from
sql job.
The trans. replication are running fine execpt the subscriber3. This
subsciber always get sthe subscription expires errors, but the monitor
article does get updated. And the wired thing is the replication monitor on
the distribution server shows that the agent is in suspect and no reponse
within 10 min after each snapshot/initation.
I did query the MSDistribution_History and there is only one row which the
date I ran the snspshot. All the retention and history period are default.
Does anyone knows that it is Win2003 to Win2000 issue or something else.
Thanks in advance
This guy expired prematurely because your history retention is less than
your publication retention. Bump this setting up to your publication
retention, and be highly proactive about sensing when this guy has dropped
off the network for more than 1 day.
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
"kc" <kc@.discussions.microsoft.com> wrote in message
news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> I have setup transaction replication using seperate server for
distribution
> box.
> Server A - Publisher (Win2003, SQL2000 SP818)
> Server B - Distributor (Win2003, SQL2000 SP818)
> Server C - Subscriber1 (Win2003 and SQL2000 SP818)
> Server D - Subscriber2 (Win2003 and SQL2000 SP818)
> Server E - Subscriber3 (Win2000, SQL2000 SP818)
> Server A has 3 publishers and each publisher has more than 10 articles,
one
> of them we use it for monitoring replication by update a datetime column
from
> sql job.
> The trans. replication are running fine execpt the subscriber3. This
> subsciber always get sthe subscription expires errors, but the monitor
> article does get updated. And the wired thing is the replication monitor
on
> the distribution server shows that the agent is in suspect and no reponse
> within 10 min after each snapshot/initation.
> I did query the MSDistribution_History and there is only one row which the
> date I ran the snspshot. All the retention and history period are
default.
> Does anyone knows that it is Win2003 to Win2000 issue or something else.
> Thanks in advance
|||In my case, the monitor article in the subscriber had same time as the
publisher when it was mark for expiration. Therefore it is not a network
issue.
By default, the hsitory rentention is 48 hrs and transaction rentention is
72 hrs, so I don't understand what do you mean that I need to bump the
setting up?
Thanks
KC
"Hilary Cotter" wrote:

> This guy expired prematurely because your history retention is less than
> your publication retention. Bump this setting up to your publication
> retention, and be highly proactive about sensing when this guy has dropped
> off the network for more than 1 day.
> --
> 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
> "kc" <kc@.discussions.microsoft.com> wrote in message
> news:7B0A51D7-F9BD-4281-A7F3-E8144164F02A@.microsoft.com...
> distribution
> one
> from
> on
> default.
>
>