Hi Kiran,
Unless you are using compressed snapshot which has a 2GB per file and
overall cab file size limit, there is no built-in limit on snapshot file
sizes. Having said that, as the size of your database grows, you may want to
consider a different initialization strategy for replication such as using
backup\restore (which is much better supported in SQL2005), a diff tool (one
is included with SQL2005), or breaking up you publication into smaller pieces.
We have also discovered recently that there is a 2^31 - 1 rows limit in bcp
that should not be a problem with the 64bit SQL Server ODBC driver. This
limit is also much less of an issue for Transactional\Snapshot publications
in SQL2005 since the snapshot agent will attempt to break up a large table
into smaller partitions to be bcp'd out (you must have a clustered primary
key on your table if you enable concurrent snapshot)
-Raymond
[quoted text, click to view] "Kiran" wrote:
> Hello,
> we have merge replication setup on sql2000 sp3 with all the hotfixes. Every
> year we do our rollout of the database. This year we are just concerned with
> the size of our database. we have 8 gb of databse and just wandering if we
> are going to run into any issues with creating a snapshot file. Is there a
I m also a novice to this but try this.
Please read this article from books online in your SQL server books online in your SQL server.
'Transferring Snapshots' It says that 20 GB ( snapshot file ) is bulky. If u r still concerned then try out applying the snapshot manually. A snapshot file has five components
If agent gives an error in dri file check your constraints.
If agent gives error in sch file then check for existance of a table with sam name that could not be deleted.
for more check out
Applying the Initial Snapshot from books online in your SQL server books online in your SQL server.
and logically map the file to the error source.
Rajesh
P.S. Please respond at r20j@yahoo.co.in I will try to help you.
**********************************************************************
Sent via Fuzzy Software @
http://www.fuzzysoftware.com/
