"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:uo8FoNNKFHA.2936@TK2MSFTNGP15.phx.gbl...
> no, you will have to then apply your schema through a pre-snapshot
command,
> and ensure you use the delete existing data in the snapshot tab of the
table
> article properties.
>
> --
> 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
>
> "frankm" <frankm@nospam.postalias> wrote in message
> news:OwVk18MKFHA.3500@TK2MSFTNGP14.phx.gbl...
> > I have a database with 3 added filegroups/files. The restore with move,
> > moves the logical filename to a specifiic physical file.
> > Once restored the db objects should be restored to their proper
> filegroups.
> >
> > Once I run the snapshot, can all of the schema and data be pushed to the
> > PRIMARY/DEFAULT filegroup?
> > Because this is what appears to be happening, all objects are being
pushed
> > into the PRIMARY/DEFAULT filegroup.
> > In published db, objects are in their correct filegroups, in the
> subscriber
> > db, they are all in the PRIMARY/DEFAULT.
> >
> > Does this sound right... I posted a database restore question to the
> server
> > ng. I'm wondering if replication could cause this.
> > This doesn't make any sense to me...
> >
> >
>
>

"frankm" <frankm@nospam.postalias> wrote in message
news:O9RjwUNKFHA.3500@TK2MSFTNGP14.phx.gbl...
> Then it sounds like replication is actually pushing the schema and data to
> the PRIMARY/DEFAULT filegroup.
> I'm still trying to understand why it does that?
>
> Looking at the "delete existing data" selection - this appears to be per
> table.
> Is there a way to set this globally? I'd hate to select that for 700
tables
> individually.
>
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
> news:uo8FoNNKFHA.2936@TK2MSFTNGP15.phx.gbl...
> > no, you will have to then apply your schema through a pre-snapshot
> command,
> > and ensure you use the delete existing data in the snapshot tab of the
> table
> > article properties.
> >
> > --
> > 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
> >
> > "frankm" <frankm@nospam.postalias> wrote in message
> > news:OwVk18MKFHA.3500@TK2MSFTNGP14.phx.gbl...
> > > I have a database with 3 added filegroups/files. The restore with
move,
> > > moves the logical filename to a specifiic physical file.
> > > Once restored the db objects should be restored to their proper
> > filegroups.
> > >
> > > Once I run the snapshot, can all of the schema and data be pushed to
the
> > > PRIMARY/DEFAULT filegroup?
> > > Because this is what appears to be happening, all objects are being
> pushed
> > > into the PRIMARY/DEFAULT filegroup.
> > > In published db, objects are in their correct filegroups, in the
> > subscriber
> > > db, they are all in the PRIMARY/DEFAULT.
> > >
> > > Does this sound right... I posted a database restore question to the
> > server
> > > ng. I'm wondering if replication could cause this.
> > > This doesn't make any sense to me...
> > >
> > >
> >
> >
>
>

"frankm" <frankm@nospam.postalias> wrote in message
news:OwVk18MKFHA.3500@TK2MSFTNGP14.phx.gbl...
> I have a database with 3 added filegroups/files. The restore with move,
> moves the logical filename to a specifiic physical file.
> Once restored the db objects should be restored to their proper
filegroups.
>
> Once I run the snapshot, can all of the schema and data be pushed to the
> PRIMARY/DEFAULT filegroup?
> Because this is what appears to be happening, all objects are being pushed
> into the PRIMARY/DEFAULT filegroup.
> In published db, objects are in their correct filegroups, in the
subscriber
> db, they are all in the PRIMARY/DEFAULT.
>
> Does this sound right... I posted a database restore question to the
server
> ng. I'm wondering if replication could cause this.
> This doesn't make any sense to me...
>
>