Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts

Monday, March 26, 2012

Replication scenario question...Merge or Transactional?

The situation I am faced with is we have a web application supported by a SQL
2000(sp4) database that resides on a limited bandwidth network. Our
distributed users are constantly complaining of "slow" response times. Our
local users have no such complaints. Some of our leadership has suggested
sending a SQL server/IIS server to the remote location and using some type of
replication to synchronize the data between these boxes. The requirements
are for minimal latency and concurrent updating of data. The leadership also
want this solution to be completely automated (little or no supervision of
the replication process) and as with everything we do they want it right away
(we're talking days, not weeks). I am very new to replication and have read
through the BOL section and am in the process of reading Hillary Cotter's
book. I am leaning toward an implementation of Merge Replication but I am
unsure if this is the right solution. Any advice or informed opinions would
be greatly appreciated.
There is no concurrent replication option ie each solution will have a degree
of latency. If you use merge then you can select from a variety of conflict
resolvers and easily work offline. This might be your best option. There are
alternatives - queued updating subscribers, immediate updating subscribers
and bidirectional transactional replication. Do you have BLOBS in the table?
Are the subscribers always connected? Should they be able to continue if not
connected? These questions will clarify and narrow down the options a bit.
Whichever option you select, don't rush - you'll need time to configure it in
a test environment to establish a set of protocols (change management, error
handling...) and to simply verify that it all works for your situation.
HTH,
Paul Ibison
"Dave Stokes" wrote:

> The situation I am faced with is we have a web application supported by a SQL
> 2000(sp4) database that resides on a limited bandwidth network. Our
> distributed users are constantly complaining of "slow" response times. Our
> local users have no such complaints. Some of our leadership has suggested
> sending a SQL server/IIS server to the remote location and using some type of
> replication to synchronize the data between these boxes. The requirements
> are for minimal latency and concurrent updating of data. The leadership also
> want this solution to be completely automated (little or no supervision of
> the replication process) and as with everything we do they want it right away
> (we're talking days, not weeks). I am very new to replication and have read
> through the BOL section and am in the process of reading Hillary Cotter's
> book. I am leaning toward an implementation of Merge Replication but I am
> unsure if this is the right solution. Any advice or informed opinions would
> be greatly appreciated.

Wednesday, March 21, 2012

Replication problems after SP4 upgrade

Hi,
We're experiencing a problem with transaction replication on SP4.
The snapshot is taken without any problems and applies, however, when it
comes to processing the additional transactions which have taken place since
the snaphot, the process starts processing in parrallel and blocks itself.
The process eventually fails and rollbacks.
This used to work fine on SP3a, but not any more... anyone any ideas?
Thanks in advance
Dave
Dave Wall
what do you mean by processing in parallel? Can you log the output to a text
file and post it here.
Follow these step on how to enable logging.
http://support.microsoft.com/default...b;en-us;312292
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
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:3B4815C4-7438-4C5C-8F81-B9720EB1B0B3@.microsoft.com...
> Hi,
> We're experiencing a problem with transaction replication on SP4.
> The snapshot is taken without any problems and applies, however, when it
> comes to processing the additional transactions which have taken place
since
> the snaphot, the process starts processing in parrallel and blocks itself.
> The process eventually fails and rollbacks.
> This used to work fine on SP3a, but not any more... anyone any ideas?
> Thanks in advance
> Dave
> --
> Dave Wall
|||Hi Dave, it would be great if you can post the [abridged] result of sp_who2
on the distributor\subscriber (or wherever the blocking occurs) as well.
Thanks.
-Raymond
"Dave Wall" wrote:

> Hi,
> We're experiencing a problem with transaction replication on SP4.
> The snapshot is taken without any problems and applies, however, when it
> comes to processing the additional transactions which have taken place since
> the snaphot, the process starts processing in parrallel and blocks itself.
> The process eventually fails and rollbacks.
> This used to work fine on SP3a, but not any more... anyone any ideas?
> Thanks in advance
> Dave
> --
> Dave Wall
|||Hi Raymond,
Got the thing sorted last night. Two things helped. The first was to
increase the minimum query plan threshold for considering paralell execution.
Secondly - we found that our networks team hadn't set the server up with PAE
extensions and so SQL wasn't using all the memory i'd assigned it. Once
these two were changed - replication went through first time.
Looks like a similar problem we had with a another server (see another post)
were processes were blocking themselves. Without the additional memory, IO
went through the roof and the spids started blocking themselves (whilst
waiting for IO)
Sorted the memory, and alls well now.
Thanks
Dave
Dave Wall
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Hi Dave, it would be great if you can post the [abridged] result of sp_who2
> on the distributor\subscriber (or wherever the blocking occurs) as well.
> Thanks.
> -Raymond
> "Dave Wall" wrote:
|||Dave,
Am curious which server needed the extra memory. Was it pub, sub, or
dist?
Thanks
Mark Andersen

Friday, March 9, 2012

Replication on MSDE2000 and db size problem

Hi,
We have following scenario:
2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
failover backup. DBs are connected by merge replication where backup is as
subscriber.
The problem is related to one table with binary column (2K) and its growing
size (over 100MB per day).
sp_spaceused product_map
name rows reserved data index_size unused
Product_map 24238 1056648KB 130448KB 13520KB 912640KB
It seems that on insert rows server allocates more space than need. This
problem occures only when system works on publisher db. It is ok when I
switch it to backup PC.
I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
don't observe the problem like this.
could you help me how to diagnose it more deeply and solve the problem?
Janek
A couple of points 1) are you using text in row?
2) Are you sure the data in this column is the same on the publisher and
subscriber. Depending on how you update your text or image data it may not
be replicated.
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
"Janek" <Janek@.discussions.microsoft.com> wrote in message
news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
> Hi,
> We have following scenario:
> 2 PC on WinXP + MSDE2000 + SP4 with production db. Secondary PC works as
> failover backup. DBs are connected by merge replication where backup is as
> subscriber.
> The problem is related to one table with binary column (2K) and its
> growing
> size (over 100MB per day).
> sp_spaceused product_map
> name rows reserved data index_size
> unused
> Product_map 24238 1056648KB 130448KB 13520KB 912640KB
> It seems that on insert rows server allocates more space than need. This
> problem occures only when system works on publisher db. It is ok when I
> switch it to backup PC.
> I have the same systems on W2k + MSDE2000 + SP3a + merge replication and
> don't observe the problem like this.
> could you help me how to diagnose it more deeply and solve the problem?
> Janek
|||1) data type for table is: int, smallint, int, char(11), smallint, smallint,
binary(2001), bit, datetime, int
2) All data is replicating, I can see it on reports on each machines. From
sp_spaceused report I see almost 1GB of unused space.
I know only one workaround:
dbcc dbreindex (.... + shrink db - a few cycles makes db to similar
backup db size.
At the moment system is working on backup PC without problem and new data is
refreshed to publisher.
Janek
"Hilary Cotter" wrote:

> A couple of points 1) are you using text in row?
> 2) Are you sure the data in this column is the same on the publisher and
> subscriber. Depending on how you update your text or image data it may not
> be replicated.
> --
> 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
>
> "Janek" <Janek@.discussions.microsoft.com> wrote in message
> news:456DC0D6-FEDC-43BF-8A22-B6CE22069464@.microsoft.com...
>
>

Wednesday, March 7, 2012

Replication Monitor - Publisher is empty, but my replication is still there and working

I have a wired situation..!
I set up transactional replication on one of my development server (SQL
2000 Dev Edition with sp4).
It is running fine without any issues and all of a sudden, i noticed in
my repication monitor tab under Publisher where I usually see the
publication is empty now.
I do see the snapshot agent, log reader and distribution agent under my
agents inside the replication Monitor. But its usefull to see all 3
agents in one window under publisher before. What happend? Is there any
way to get that inside that monitor? Has someone encountered this
sitation before? Please advise...
After that I tried to create a new set of replication on different
database on the same server and i dont see those either under
Replication Monitor - Publishers...
All it says is (No Items)...
I would appreciate any help to correct this issue... Thanks in advance..
Which account are you using to connect to the EM?
"Query Builder" <querybuilder@.gmail.com> wrote in message
news:1162496955.745756.103220@.e3g2000cwe.googlegro ups.com...
>I have a wired situation..!
> I set up transactional replication on one of my development server (SQL
> 2000 Dev Edition with sp4).
> It is running fine without any issues and all of a sudden, i noticed in
> my repication monitor tab under Publisher where I usually see the
> publication is empty now.
> I do see the snapshot agent, log reader and distribution agent under my
> agents inside the replication Monitor. But its usefull to see all 3
> agents in one window under publisher before. What happend? Is there any
> way to get that inside that monitor? Has someone encountered this
> sitation before? Please advise...
> After that I tried to create a new set of replication on different
> database on the same server and i dont see those either under
> Replication Monitor - Publishers...
> All it says is (No Items)...
> I would appreciate any help to correct this issue... Thanks in advance..
>
|||I think your subscription has expired and being dropped. Check to see if the
job exists in the jobs folder, it will have a name similar to the
publication.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"Query Builder" <querybuilder@.gmail.com> wrote in message
news:1162496955.745756.103220@.e3g2000cwe.googlegro ups.com...
>I have a wired situation..!
> I set up transactional replication on one of my development server (SQL
> 2000 Dev Edition with sp4).
> It is running fine without any issues and all of a sudden, i noticed in
> my repication monitor tab under Publisher where I usually see the
> publication is empty now.
> I do see the snapshot agent, log reader and distribution agent under my
> agents inside the replication Monitor. But its usefull to see all 3
> agents in one window under publisher before. What happend? Is there any
> way to get that inside that monitor? Has someone encountered this
> sitation before? Please advise...
> After that I tried to create a new set of replication on different
> database on the same server and i dont see those either under
> Replication Monitor - Publishers...
> All it says is (No Items)...
> I would appreciate any help to correct this issue... Thanks in advance..
>
|||I am connected thru EM using the SA account. I also have adimin rights
thru windows authentication...
How do I check my subscriptions are expired or not? I created a new
replication for testing and it is also working fine but i dont see the
replication in the replication monitor.. I do see the publications
under the replication--> publication tree...
THanks for all your input. I would apprecate if you can help me figure
this out...! Thanks again
On Nov 3, 6:34 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> I think your subscription has expired and being dropped. Check to see if the
> job exists in the jobs folder, it will have a name similar to the
> publication.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "Query Builder" <querybuil...@.gmail.com> wrote in messagenews:1162496955.745756.103220@.e3g2000cwe.go oglegroups.com...
>
>
>
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> I am connected thru EM using the SA account. I also have adimin rights
> thru windows authentication...
> How do I check my subscriptions are expired or not? I created a new
> replication for testing and it is also working fine but i dont see the
> replication in the replication monitor.. I do see the publications
> under the replication--> publication tree...
> THanks for all your input. I would apprecate if you can help me figure
> this out...! Thanks again
>
> On Nov 3, 6:34 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
|||I still have this issue.. Any thoughts? ... ideas.. ?
Thanks in advance..
Query Builder wrote:[vbcol=seagreen]
> I am connected thru EM using the SA account. I also have adimin rights
> thru windows authentication...
> How do I check my subscriptions are expired or not? I created a new
> replication for testing and it is also working fine but i dont see the
> replication in the replication monitor.. I do see the publications
> under the replication--> publication tree...
> THanks for all your input. I would apprecate if you can help me figure
> this out...! Thanks again
>
> On Nov 3, 6:34 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
|||I finally figured out the issue... I had the sql names changed.. when I
changed it back, the replications appeared under the replication
monitor tab...
So the moral of the whole story(issue) is never change SQL jobs
associated with replication.. It will disspear from the replication
monitor group...
Query Builder wrote:[vbcol=seagreen]
> I still have this issue.. Any thoughts? ... ideas.. ?
> Thanks in advance..
> Query Builder wrote:

Saturday, February 25, 2012

Replication issues with failed logins

I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.

Any suggestions would be greatly appreciated!

Thanks!

For those who experience similar problems: I simply ran distribution agent at Distributor. That fixed the issue.

Replication issues after a Database Restore - Unable to drop or create Transactional Repli

Hi,

I have transactional replication set up on on of our MS SQL 2000 (SP4)
Std Edition database server

Because of an unfortunate scenario, I had to restore one of the
publication databases. I scripted the replication module and dropped
the publication first. Then did a full restore.

When I try to set up the replication thru the script, it created the
publication with the following error message

Server: Msg 2714, Level 16, State 5, Procedure SYNC_FCR To
GPRPTS_GL00100, Line 1
There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in the
database.

It seems the previous replication has set up these system views
SYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replication
module again to see if it drops the views but it didn't.

The replication fails with some wired error & complains about this
views when I try to run the synch..

I even tried running the sp_removedbreplication to drop the
replication module, but the views do not seem to disappear.

My question is how do I remove these system views or how do I make the
replication work without using these views or create new views.. Why
is this creating those system views in the first place?

I would appreciate if anyone can help me fix this issue. Please feel
free to let me know if any additional information or scripts needed.

Thanks in advance..

Regards,
Aravin Rajendra.you should be able to drop them using query analyzer.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

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
"Query Builder" <querybuilder@.gmail.comwrote in message
news:1189702889.303360.189580@.o80g2000hse.googlegr oups.com...

Quote:

Originally Posted by

Hi,
>
I have transactional replication set up on on of our MS SQL 2000 (SP4)
Std Edition database server
>
Because of an unfortunate scenario, I had to restore one of the
publication databases. I scripted the replication module and dropped
the publication first. Then did a full restore.
>
When I try to set up the replication thru the script, it created the
publication with the following error message
>
Server: Msg 2714, Level 16, State 5, Procedure SYNC_FCR To
GPRPTS_GL00100, Line 1
There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in the
database.
>
It seems the previous replication has set up these system views
SYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replication
module again to see if it drops the views but it didn't.
>
The replication fails with some wired error & complains about this
views when I try to run the synch..
>
I even tried running the sp_removedbreplication to drop the
replication module, but the views do not seem to disappear.
>
My question is how do I remove these system views or how do I make the
replication work without using these views or create new views.. Why
is this creating those system views in the first place?
>
I would appreciate if anyone can help me fix this issue. Please feel
free to let me know if any additional information or scripts needed.
>
Thanks in advance..
>
Regards,
Aravin Rajendra.
>

|||Thanks for your response.. I tried dropping it thru QA.. Now the
replication doesn't show up on the publication. But the replication
monitor still has this replication with a failed status....

Can you please point me to the direction on safely removing all
components of a particular replication module (I have other publishers
in this server)..

Thanks again..

Aravin Rajendar.

On Sep 13, 2:37 pm, "Hilary Cotter" <hilary.cot...@.gmail.comwrote:

Quote:

Originally Posted by

you should be able to drop them using query analyzer.
>
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
>
Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
>
Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com"Query Builder" <querybuil...@.gmail.comwrote in message
>
news:1189702889.303360.189580@.o80g2000hse.googlegr oups.com...
>

Quote:

Originally Posted by

Hi,


>

Quote:

Originally Posted by

I have transactional replication set up on on of our MS SQL 2000 (SP4)
Std Edition database server


>

Quote:

Originally Posted by

Because of an unfortunate scenario, I had to restore one of the
publication databases. I scripted the replication module and dropped
the publication first. Then did a full restore.


>

Quote:

Originally Posted by

When I try to set up the replication thru the script, it created the
publication with the following error message


>

Quote:

Originally Posted by

Server: Msg 2714, Level 16, State 5, Procedure SYNC_FCR To
GPRPTS_GL00100, Line 1
There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in the
database.


>

Quote:

Originally Posted by

It seems the previous replication has set up these system views
SYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replication
module again to see if it drops the views but it didn't.


>

Quote:

Originally Posted by

The replication fails with some wired error & complains about this
views when I try to run the synch..


>

Quote:

Originally Posted by

I even tried running the sp_removedbreplication to drop the
replication module, but the views do not seem to disappear.


>

Quote:

Originally Posted by

My question is how do I remove these system views or how do I make the
replication work without using these views or create new views.. Why
is this creating those system views in the first place?


>

Quote:

Originally Posted by

I would appreciate if anyone can help me fix this issue. Please feel
free to let me know if any additional information or scripts needed.


>

Quote:

Originally Posted by

Thanks in advance..


>

Quote:

Originally Posted by

Regards,
Aravin Rajendra.