Compressed Snapshot Files!

Hello All,
I'm using Transactional Replication. I have compress snapshot file now I
want to configure it on Subscriber.
I saw BOL and it says,
1. In Microsoft SQL Server Enterprise Manager, expand the subscription
database and the Subscriptions directory, right- click a subscription,
and then click Properties.
but didnt find the Subscription directory under subscription database.
How can I configure?
Thanks in advance.
Naveed.
the snapshot files will be compressed in the cab format in your alternate
snapshot folder. If you are doing a pull subscription you have the option to
applying the snapshot (compressed or uncompressed) from an alternate
location by using the "Use snapshot files from the following folder option."
You will have to prove a path to the root of the snapshot location, ie
\\PublisherServerName\Share\ where this will map to c:\temp or wherever you
place your files in. If you copy these files locally you have to copy the
directory structure from unc on, ie if you place the files in c:\temp you
would copy the contents of unc to c:\temp.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:OoosGusqEHA.2732@.TK2MSFTNGP09.phx.gbl...
> Hello All,
> I'm using Transactional Replication. I have compress snapshot file now I
> want to configure it on Subscriber.
> I saw BOL and it says,
> 1. In Microsoft SQL Server Enterprise Manager, expand the subscription
> database and the Subscriptions directory, right- click a
subscription,
> and then click Properties.
> but didnt find the Subscription directory under subscription database.
> How can I configure?
> Thanks in advance.
> Naveed.
>
|||Hello Hilary!!!
Thanks for your reply, You gave solution for Pull Subscription But We are
using Push Subscription and we have very slow connection for publishing data
on subscriber, i.e why we compress snapshot file in alternate location and
now we want to configure it on subscriber.
How to do that?
Thanks,
Naveed.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eQGmKXtqEHA.3416@.TK2MSFTNGP15.phx.gbl...
> the snapshot files will be compressed in the cab format in your alternate
> snapshot folder. If you are doing a pull subscription you have the option
to
> applying the snapshot (compressed or uncompressed) from an alternate
> location by using the "Use snapshot files from the following folder
option."
> You will have to prove a path to the root of the snapshot location, ie
> \\PublisherServerName\Share\ where this will map to c:\temp or wherever
you
> place your files in. If you copy these files locally you have to copy the
> directory structure from unc on, ie if you place the files in c:\temp you
> would copy the contents of unc to c:\temp.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Naveed" <nrehman@.marsonssoft.com> wrote in message
> news:OoosGusqEHA.2732@.TK2MSFTNGP09.phx.gbl...
> subscription,
>
|||use the -AltSnapshotFolder switch on your distribution agent. make sure you
uncheck the generate snapshot in the default folder location for your
snapshot properties.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Naveed" <nrehman@.marsonssoft.com> wrote in message
news:eUFealtqEHA.376@.TK2MSFTNGP14.phx.gbl...
> Hello Hilary!!!
> Thanks for your reply, You gave solution for Pull Subscription But We are
> using Push Subscription and we have very slow connection for publishing
data[vbcol=seagreen]
> on subscriber, i.e why we compress snapshot file in alternate location and
> now we want to configure it on subscriber.
> How to do that?
> Thanks,
> Naveed.
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eQGmKXtqEHA.3416@.TK2MSFTNGP15.phx.gbl...
alternate[vbcol=seagreen]
option[vbcol=seagreen]
> to
> option."
> you
the[vbcol=seagreen]
you[vbcol=seagreen]
I[vbcol=seagreen]
subscription
>
sqlsql

Comparison of different replication types

Greetings,
I'm looking for a document that does a really good comparison of merge
replication, peer-to-peer transactional replication, and transactional
replication with updating subscribers. Does anyone know of a site or
document with such a comparison? I would especially be interested in
scalability/performance information regarding the different types of
replication.
Thanks,
Sam Bendayan
DB Architect
Ultimate Software
sam.bendayan@.gmail.com
*** Sent via Developersdex http://www.codecomments.com ***
Also, I found in one of the blog posts a statement saying that
Peer-To-Peer replication does not scale well beyond 10 nodes. Just to
be perfectly clear, does this mean that if you have more than 10 servers
in the replication topology then you will start to see performance
problems and that there is no good solution to this?
It also states that merge replication is better for a large number of
nodes. Is it possible to have these larger number of nodes synchronized
frequently (every few minutes), or will that not scale well either?
Thanks,
SB
Sam Bendayan
DB Architect
Ultimate Software
sam.bendayan@.gmail.com
*** Sent via Developersdex http://www.codecomments.com ***
|||In a PASS talk on SQL Server 2005 Replication, Philip Vaughn the Microsoft
program manager for Replication said that (IIRC) between 10-15 nodes the
network links become saturated and he did not recommend scaling it beyond
this number.
Regarding scaling merge replication, you have to look at hierarchies.
Depending on the amount of data you sync with each subscriber each time you
might have to limit the number of concurrent merge processes.
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
"Sam Bendayan" <sam.bendayan@.gmail.com> wrote in message
news:u4DP5YFvHHA.3724@.TK2MSFTNGP03.phx.gbl...
> Also, I found in one of the blog posts a statement saying that
> Peer-To-Peer replication does not scale well beyond 10 nodes. Just to
> be perfectly clear, does this mean that if you have more than 10 servers
> in the replication topology then you will start to see performance
> problems and that there is no good solution to this?
> It also states that merge replication is better for a large number of
> nodes. Is it possible to have these larger number of nodes synchronized
> frequently (every few minutes), or will that not scale well either?
> Thanks,
> SB
> Sam Bendayan
> DB Architect
> Ultimate Software
> sam.bendayan@.gmail.com
> *** Sent via Developersdex http://www.codecomments.com ***