"Franky" <Franky@discussions.microsoft.com> wrote in message
news:93351328-0D4B-4784-9476-83D44D4EC8AC@microsoft.com...
> Hallo,
>
> can someone explain this problem/suggest a solution
> I made server A publisher and server B distributor.
> On server A I had a database base1 which had a size of 70 GB and contains
1200 tables. I restored a backup of that database on server B.
> I made a publication on server A for database base1. Made the script for

> Then I created the pull subscription on server B databas base1.
>
> This all works fine.
>
> I tried to do the same with a database base2 with a size of 22 GB, but
which contains 28000 tables.( on the same servers.)
> Then when I try to create the pull subscription the tempdb on server A
grows until all the diskspace is used (96 GB).
>
> thx
>

"Hilary Cotter" wrote:

> Are you doing a no-sync subscription?
>
> Can you log the agent which is failing to find out exactly what it is doing?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
>
> "Franky" <Franky@discussions.microsoft.com> wrote in message
> news:93351328-0D4B-4784-9476-83D44D4EC8AC@microsoft.com...
> > Hallo,
> >
> > can someone explain this problem/suggest a solution
> > I made server A publisher and server B distributor.
> > On server A I had a database base1 which had a size of 70 GB and contains
> 1200 tables. I restored a backup of that database on server B.
> > I made a publication on server A for database base1. Made the script for
> the necessary replication stored procedures and created them on base1 on
> server B.
> > Then I created the pull subscription on server B databas base1.
> >
> > This all works fine.
> >
> > I tried to do the same with a database base2 with a size of 22 GB, but
> which contains 28000 tables.( on the same servers.)
> > Then when I try to create the pull subscription the tempdb on server A
> grows until all the diskspace is used (96 GB).
> >
> > thx
> >
>
>