Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Publish Subscription replication - Side effects?

 
   Database Forums (Home) -> Replication RSS
Next:  Create nested stored procedure help  
Author Message
Jim Millar

External


Since: Dec 20, 2007
Posts: 2



(Msg. 1) Posted: Thu Dec 20, 2007 3:03 pm
Post subject: Publish Subscription replication - Side effects?
Archived from groups: microsoft>public>sqlserver>replication (more info?)

Hi Guys,

I've been given the task of creating a disaster recovery "replica" of a
production SQL server and keeping it current.
(SQL 2000)

At first we thought of using scripts to do a backup/restore method.
But a couple of the databases are upwards of a hundred gigabytes...
A bit hard on drive space.

I thought a better method would be to replicate the databases using the
Publish and "push subscriptions".
I'm not very knowledgeable about SQL management, However with the help of
Google and a little time,
I mamnaged to make it work experimentally with the Northwind database.
But that's tiny compared to the live DBs

My question is:
Am I likely to see any 'unforseen' side effects of replicating by this
method?

Thanks,
Jim

 >> Stay informed about: Publish Subscription replication - Side effects? 
Back to top
Login to vote
Warren Brunk

External


Since: Sep 08, 2006
Posts: 57



(Msg. 2) Posted: Thu Dec 20, 2007 9:56 pm
Post subject: Re: Publish Subscription replication - Side effects? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

To keep maximum performance on your main SQL Server I would consider
"pulling" the transactionally replicated data.

This article from Microsoft has alot of great tips on how to maximize
replication performance.

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx

If you have money for a nice SAN unit you can check out Split Mirroring.

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx



--

/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/


"Jim Millar" wrote in message

> Hi Guys,
>
> I've been given the task of creating a disaster recovery "replica" of a
> production SQL server and keeping it current.
> (SQL 2000)
>
> At first we thought of using scripts to do a backup/restore method.
> But a couple of the databases are upwards of a hundred gigabytes...
> A bit hard on drive space.
>
> I thought a better method would be to replicate the databases using the
> Publish and "push subscriptions".
> I'm not very knowledgeable about SQL management, However with the help of
> Google and a little time,
> I mamnaged to make it work experimentally with the Northwind database.
> But that's tiny compared to the live DBs
>
> My question is:
> Am I likely to see any 'unforseen' side effects of replicating by this
> method?
>
> Thanks,
> Jim
>

 >> Stay informed about: Publish Subscription replication - Side effects? 
Back to top
Login to vote
Jim Millar

External


Since: Dec 20, 2007
Posts: 2



(Msg. 3) Posted: Fri Dec 21, 2007 7:13 am
Post subject: Re: Publish Subscription replication - Side effects? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Thanks Warren!

I'll give it a go.
Unfortunately the client is 'cheap' and wants to spend as little as
possible.
Getting to be par for the course these days...


"Warren Brunk" wrote in message

> To keep maximum performance on your main SQL Server I would consider
> "pulling" the transactionally replicated data.
>
> This article from Microsoft has alot of great tips on how to maximize
> replication performance.
>
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
>
> If you have money for a nice SAN unit you can check out Split Mirroring.
>
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
>
>
>
> --
>
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
>
> "Jim Millar" wrote in message
>
>> Hi Guys,
>>
>> I've been given the task of creating a disaster recovery "replica" of a
>> production SQL server and keeping it current.
>> (SQL 2000)
>>
>> At first we thought of using scripts to do a backup/restore method.
>> But a couple of the databases are upwards of a hundred gigabytes...
>> A bit hard on drive space.
>>
>> I thought a better method would be to replicate the databases using the
>> Publish and "push subscriptions".
>> I'm not very knowledgeable about SQL management, However with the help of
>> Google and a little time,
>> I mamnaged to make it work experimentally with the Northwind database.
>> But that's tiny compared to the live DBs
>>
>> My question is:
>> Am I likely to see any 'unforseen' side effects of replicating by this
>> method?
>>
>> Thanks,
>> Jim
>>
>
>
 >> Stay informed about: Publish Subscription replication - Side effects? 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Effects of reboot on SQL2005 Merge Replication? - Hi, Can anyone confirm what happens when either of 2 SQL 2005 servers configured for continous merge replication are rebooted? Will the replication just pick up and carry on, or must it be manually started again? Many thanks, FD

stored_procedure execution replication on No-sync subscrip.. - is it possible to add stored_procedure execution replication to non- sync transactional replication ? I can't find BOL docs about this. I can add it to the publication but nothing is logged on the distributor when I invoke it. Any thoughts ?

3930 when pushing subscription to a snapshot replication p.. - We are attempting to use snapshot replication to push data from one SQL Server 2005 server to another SQL Server 2005 server. We had no trouble creating the publication, but when we try to create a new push subscription we get the failure below..

Tips on replication (mssql 2000), subscription marked inac.. - Hi guys. Every now and then, replication on my transactional publications keep getting "red" with errors. Always the error is : "The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be...

FKs don't publish? - I am using SQL2005 SP2 and noticed that the foreign keys don't publish to the subscribers. Is this normal? Thanks, Peter Cwik
   Database Forums (Home) -> Replication All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]