Hello all and thank you in advance:
Question 1) Can I use merge replication with tables that IMAGE data
type columns?
Question 2) I need to add my uniqueidenity, if I add to the bottom of
the column list can be sure that ALTER statement will be transparant
and not lock the entire table?
Thank VERY much,
Erik
Yes - merge replication can handle text/image datatypes. This is one factor
that distinguishes it from queued updating subscribers.
I don't follow your other question. Merge uses a column containing a
uniqueidentifier and which has the RowGuid attribute. Only one column can
have this attribute although there can be several columns containing
uniqueidentifiers. Adding in other columns using sp_repladdcolumn with a
default should be fine, or using ALTER TABLE in SQL 2005. Altering the schema
of the table will lock the table whichever way you do it.
Cheers,
Paul Ibison
Showing posts with label type. Show all posts
Showing posts with label type. Show all posts
Wednesday, March 28, 2012
Wednesday, March 21, 2012
Merge Replication programming with SQL Snapshot and SQL Distribution Control
Hello all, I am try to implement Merge replication just
like this
article shows for transaction type replicaion
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;319649
using SQL Snapshot and SQL Distribution Control with
Visual C# .NET
First ..I dont see
Use a Distribution Agent that is independent of other
publications from this database and Snapshot files are
always available to initialize new subscriptions
immediately check boxes under subscription options.
second..
I get an error on SQL Snapshot object initialization
Erro # 24006 and message : The publication does not exist.
Sri,
you're using the wrong article - the one you have applies to transactional
and snapshot. For merge, have a look at this one:
http://support.microsoft.com/default...b;EN-US;319647
HTH,
Paul Ibison
|||Paul, Thank you very much.It worked like a charm.
Once again Thanks a million.
Srinu
>--Original Message--
>Sri,
>you're using the wrong article - the one you have applies
to transactional
>and snapshot. For merge, have a look at this one:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;319647
>HTH,
>Paul Ibison
>
>.
>
like this
article shows for transaction type replicaion
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;319649
using SQL Snapshot and SQL Distribution Control with
Visual C# .NET
First ..I dont see
Use a Distribution Agent that is independent of other
publications from this database and Snapshot files are
always available to initialize new subscriptions
immediately check boxes under subscription options.
second..
I get an error on SQL Snapshot object initialization
Erro # 24006 and message : The publication does not exist.
Sri,
you're using the wrong article - the one you have applies to transactional
and snapshot. For merge, have a look at this one:
http://support.microsoft.com/default...b;EN-US;319647
HTH,
Paul Ibison
|||Paul, Thank you very much.It worked like a charm.
Once again Thanks a million.
Srinu
>--Original Message--
>Sri,
>you're using the wrong article - the one you have applies
to transactional
>and snapshot. For merge, have a look at this one:
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;319647
>HTH,
>Paul Ibison
>
>.
>
Labels:
control,
database,
distribution,
implement,
justlike,
merge,
microsoft,
mysql,
oracle,
programming,
replication,
server,
snapshot,
sql,
thisarticle,
transaction,
type
Wednesday, March 7, 2012
Merge Replication Database move to new hardware
Hello,
How to move 50GB of Publication Database to new Hardware( New SQL Server)
quickly without loosing replication inforamtion.
Replication Type : Merge
OS : Windows 2003 Server
SQL Version : SQL Server 2000
Edition : Standard
Service Pack : SP4
Best Regards
Ponnu
This can't easily be done. You are best off to rename the new SQL Server
with the name of the existing SQL Server and then restore the master, msdb,
distribution, and published databases on to the new server.
If this can't be done you will have to script out the publications and
subscriptions, drop them in current production and redeploy them on the new
server editing the scripts for the new SQL Server name.
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
"ponnu" <ponnu@.discussions.microsoft.com> wrote in message
news:A78A2B0E-AE39-4692-839A-0501E5AC0BFF@.microsoft.com...
> Hello,
> How to move 50GB of Publication Database to new Hardware( New SQL Server)
> quickly without loosing replication inforamtion.
> Replication Type : Merge
> OS : Windows 2003 Server
> SQL Version : SQL Server 2000
> Edition : Standard
> Service Pack : SP4
> Best Regards
> Ponnu
|||Thanks very much for your quick reply
I can restore master ,msdb, distribution databases.
Is there any way to attaché(sp_attach_db) published database rather than
restoring from the backup file.
I am wondering restoring the published database will take about 10
hours(55GB database size).
Please advise me the best solution.
Regards
Ponnu
"Hilary Cotter" wrote:
> This can't easily be done. You are best off to rename the new SQL Server
> with the name of the existing SQL Server and then restore the master, msdb,
> distribution, and published databases on to the new server.
> If this can't be done you will have to script out the publications and
> subscriptions, drop them in current production and redeploy them on the new
> server editing the scripts for the new SQL Server name.
> --
> 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
>
> "ponnu" <ponnu@.discussions.microsoft.com> wrote in message
> news:A78A2B0E-AE39-4692-839A-0501E5AC0BFF@.microsoft.com...
>
>
How to move 50GB of Publication Database to new Hardware( New SQL Server)
quickly without loosing replication inforamtion.
Replication Type : Merge
OS : Windows 2003 Server
SQL Version : SQL Server 2000
Edition : Standard
Service Pack : SP4
Best Regards
Ponnu
This can't easily be done. You are best off to rename the new SQL Server
with the name of the existing SQL Server and then restore the master, msdb,
distribution, and published databases on to the new server.
If this can't be done you will have to script out the publications and
subscriptions, drop them in current production and redeploy them on the new
server editing the scripts for the new SQL Server name.
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
"ponnu" <ponnu@.discussions.microsoft.com> wrote in message
news:A78A2B0E-AE39-4692-839A-0501E5AC0BFF@.microsoft.com...
> Hello,
> How to move 50GB of Publication Database to new Hardware( New SQL Server)
> quickly without loosing replication inforamtion.
> Replication Type : Merge
> OS : Windows 2003 Server
> SQL Version : SQL Server 2000
> Edition : Standard
> Service Pack : SP4
> Best Regards
> Ponnu
|||Thanks very much for your quick reply
I can restore master ,msdb, distribution databases.
Is there any way to attaché(sp_attach_db) published database rather than
restoring from the backup file.
I am wondering restoring the published database will take about 10
hours(55GB database size).
Please advise me the best solution.
Regards
Ponnu
"Hilary Cotter" wrote:
> This can't easily be done. You are best off to rename the new SQL Server
> with the name of the existing SQL Server and then restore the master, msdb,
> distribution, and published databases on to the new server.
> If this can't be done you will have to script out the publications and
> subscriptions, drop them in current production and redeploy them on the new
> server editing the scripts for the new SQL Server name.
> --
> 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
>
> "ponnu" <ponnu@.discussions.microsoft.com> wrote in message
> news:A78A2B0E-AE39-4692-839A-0501E5AC0BFF@.microsoft.com...
>
>
Labels:
50gb,
database,
hardware,
inforamtion,
loosing,
merge,
microsoft,
mysql,
oracle,
publication,
quickly,
replication,
server,
sql,
type
Subscribe to:
Posts (Atom)