Make Changes to Published Database

with the replicate_ddl setting of sp_addmergepublication set to true (1)
almost all DDL (table changes) should be replicated. Can you verify that
this is the case?
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
"Vincent Cotton" <nospam@.eldersuite.com> wrote in message
news:D03C0DA9-40D8-467C-B262-541F6CE7AE6E@.microsoft.com...
>I currently have a VB6 app that I am rewriting. I am now using Visual
> Studio 2005 and the new app will be a windows forms smart client. I am
> using SQL Server 2005 Compact Edition as the local database. I have SQL
> Server 2005 Enterprise Edition setup as a merge replication publisher. I
> will have a little over 500 subscribers. The system is not yet
> implemented;
> I am still testing at this point. The main problem I am having is when I
> want to make changes to the main database (publisher). SSMS always tells
> me
> I can't make changes because it is setup for replication. At this point
> it's not a big deal. I just remove the publication, remove the
> subscriptions, make changes to my tables and then re-establish the
> publication. However, pretty soon when my app goes into production I
> don't
> think this will work to well. I thought from all my research that I would
> be able to make changes to my tables such as adding new fields, changing
> field names, deleting fields, adding tables and so on, and that those
> changes would just propagate down to the subscribers. I'm sure I'm just
> missing something. So, my question is how can I make changes to the
> publisher without having to remove the publication/subscriptions and start
> all over?
> Thanks,
> Vince
Just to let you know I am very new to SQL Server. I am a "Micro" ISV
programmer not a dba. So, thanks in advance for your patience.
I found the replicate_ddl column in the dbo.sysmergepublications table, but
I can't open to see it's value. It is an (int,not null) and I can see its
default value is ((0)); so, I assume it's value is 0. I am using the SSMS
gui so I don't know how to proceed from here.
Thanks,
Vince
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23i8bLTQKHHA.960@.TK2MSFTNGP04.phx.gbl...
> with the replicate_ddl setting of sp_addmergepublication set to true (1)
> almost all DDL (table changes) should be replicated. Can you verify that
> this is the case?
> --
> 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
>
> "Vincent Cotton" <nospam@.eldersuite.com> wrote in message
> news:D03C0DA9-40D8-467C-B262-541F6CE7AE6E@.microsoft.com...
>

Maintenance Plans

1) Is it a good practice to use the Maintenance Plans to back up the
database, trans logs, and organize the index, and verify the data?
2) How often would it be good practice to run the recreating of index and
verifying the data?
3) Or it's better just create one jobs to backup database etc?
4) Are there any negative to using Maintenance Plans
Thank You
There are no one size fits all answer for these types of questions. If you have responsibility for
these things, then you have responsibility to understand how backup etc work in SQL Server, learn
how the maint wizard work and based on that make decisions whether maint wiz is good for your
organization. Regarding reindexing, I suggest you read
http://www.microsoft.com/technet/pro...ss2kidbp.mspx.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> 1) Is it a good practice to use the Maintenance Plans to back up the
> database, trans logs, and organize the index, and verify the data?
> 2) How often would it be good practice to run the recreating of index and
> verifying the data?
> 3) Or it's better just create one jobs to backup database etc?
> 4) Are there any negative to using Maintenance Plans
> Thank You
|||"Tibor Karaszi" wrote:

> There are no one size fits all answer for these types of questions. If you have responsibility for
> these things, then you have responsibility to understand how backup etc work in SQL Server, learn
> how the maint wizard work and based on that make decisions whether maint wiz is good for your
> organization. Regarding reindexing, I suggest you read
> http://www.microsoft.com/technet/pro...ss2kidbp.mspx.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
> news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
>
>

Maintenance Plans

1) Is it a good practice to use the Maintenance Plans to back up the
database, trans logs, and organize the index, and verify the data?
2) How often would it be good practice to run the recreating of index and
verifying the data?
3) Or it's better just create one jobs to backup database etc?
4) Are there any negative to using Maintenance Plans
Thank YouThere are no one size fits all answer for these types of questions. If you have responsibility for
these things, then you have responsibility to understand how backup etc work in SQL Server, learn
how the maint wizard work and based on that make decisions whether maint wiz is good for your
organization. Regarding reindexing, I suggest you read
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> 1) Is it a good practice to use the Maintenance Plans to back up the
> database, trans logs, and organize the index, and verify the data?
> 2) How often would it be good practice to run the recreating of index and
> verifying the data?
> 3) Or it's better just create one jobs to backup database etc?
> 4) Are there any negative to using Maintenance Plans
> Thank You|||"Tibor Karaszi" wrote:
> There are no one size fits all answer for these types of questions. If you have responsibility for
> these things, then you have responsibility to understand how backup etc work in SQL Server, learn
> how the maint wizard work and based on that make decisions whether maint wiz is good for your
> organization. Regarding reindexing, I suggest you read
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in message
> news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> > 1) Is it a good practice to use the Maintenance Plans to back up the
> > database, trans logs, and organize the index, and verify the data?
> >
> > 2) How often would it be good practice to run the recreating of index and
> > verifying the data?
> >
> > 3) Or it's better just create one jobs to backup database etc?
> >
> > 4) Are there any negative to using Maintenance Plans
> >
> > Thank You
>
>

Maintenance Plans

1) Is it a good practice to use the Maintenance Plans to back up the
database, trans logs, and organize the index, and verify the data?
2) How often would it be good practice to run the recreating of index and
verifying the data?
3) Or it's better just create one jobs to backup database etc?
4) Are there any negative to using Maintenance Plans
Thank YouThere are no one size fits all answer for these types of questions. If you h
ave responsibility for
these things, then you have responsibility to understand how backup etc work
in SQL Server, learn
how the maint wizard work and based on that make decisions whether maint wiz
is good for your
organization. Regarding reindexing, I suggest you read
http://www.microsoft.com/technet/pr...ver/default.asp
http://www.solidqualitylearning.com/
"Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in m
essage
news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
> 1) Is it a good practice to use the Maintenance Plans to back up the
> database, trans logs, and organize the index, and verify the data?
> 2) How often would it be good practice to run the recreating of index and
> verifying the data?
> 3) Or it's better just create one jobs to backup database etc?
> 4) Are there any negative to using Maintenance Plans
> Thank You|||"Tibor Karaszi" wrote:

> There are no one size fits all answer for these types of questions. If you
have responsibility for
> these things, then you have responsibility to understand how backup etc wo
rk in SQL Server, learn
> how the maint wizard work and based on that make decisions whether maint w
iz is good for your
> organization. Regarding reindexing, I suggest you read
> http://www.microsoft.com/technet/pr...ver/default.asp
> http://www.solidqualitylearning.com/
>
> "Victoria Morrison" <Victoria Morrison@.discussions.microsoft.com> wrote in
message
> news:CCA01C5B-D86A-4846-8682-50DBA0B24C37@.microsoft.com...
>
>