Replication error on tables with different owners

Hi Freinds,
SQL2000
I want to replicate a database that has tables with different schemas.
user1.invoice
user2.invoice
user2.invoice
user1.invoice_detail
user2.invoice_detail
..
..
..
When t run the snapshot, itcreates the tables for dbo and causing problems.
What are my options to roll over this error and problem?
Thanks in advance,
Pat
I assume you mean
user1.invoice
user2.invoice
user3.invoice
If this is the case, put the accounts in place in your subscriber using a
pre snapshot command. Then use sp_addarticle to create the different tables.
The @.destination_owner parameter allows you to specify different owner
names.
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
"Patrick" <patriarck@.gmail.com> wrote in message
news:OUA5aUYuFHA.904@.tk2msftngp13.phx.gbl...
> Hi Freinds,
> SQL2000
> I want to replicate a database that has tables with different schemas.
> user1.invoice
> user2.invoice
> user2.invoice
> user1.invoice_detail
> user2.invoice_detail
> .
> .
> .
> When t run the snapshot, itcreates the tables for dbo and causing
problems.
> What are my options to roll over this error and problem?
> Thanks in advance,
> Pat
>
|||So , basicly it is a manual proces for creating the article and pushing the
replication !
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e6YeGyZuFHA.1196@.TK2MSFTNGP10.phx.gbl...
>I assume you mean
> user1.invoice
> user2.invoice
> user3.invoice
> If this is the case, put the accounts in place in your subscriber using a
> pre snapshot command. Then use sp_addarticle to create the different
> tables.
> The @.destination_owner parameter allows you to specify different owner
> names.
>
>
> --
> 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
> "Patrick" <patriarck@.gmail.com> wrote in message
> news:OUA5aUYuFHA.904@.tk2msftngp13.phx.gbl...
> problems.
>
|||Well, not really. Most of the functionality is wizard driven, however to do
things outside of the scope of the wizards you have to do some manual steps.
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
"Patrick" <patriarck@.gmail.com> wrote in message
news:OG5qvuhuFHA.904@.tk2msftngp13.phx.gbl...
> So , basicly it is a manual proces for creating the article and pushing
> the replication !
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:e6YeGyZuFHA.1196@.TK2MSFTNGP10.phx.gbl...
>

Replication Error

I found a problem in replication which we have 3 tables, namely tab A, tab B and tab C

replication will apply on tab A and tab B

and there is a trigger on tab A and tab B, whenever insert/update on tab A it fires trigger to update tab b

whenever insert/update on tab B it fires trigger to update tab C

And I found the replication error from tab A on updating tab C. If I manually insert the row, it works fine.....

Any advise? Thanks in advance!

what's the error?|||

Error Code 515:

Cannot insert the value NULL into column 'amount_id', table 'dev.dbo.tab_c'; column does not allow nulls. INSERT fails.

Thanks

|||

Can you also insert value NULL successfully into column 'amount_id" of table_C manually?

-Yunjing

|||

No, actually, the column 'amount_id' is defined as 'not null'. While inserting the row into tab A, it fires the trigger and check the conditions in tab b, and then insert the row into tab c. However, I found the 'amount_id' is defined in the trigger and shouldn't be null.

I used sp_browsereplcmds to find out the command with error and manual exec the store proc.

sp_MSins_ADMTAB_A with the field values and it works. After the row inserted, the pending transactions delivered to the subscriber successfully (as I set the replication option to skip the error 2627 for duplicate primary key)

|||

Sorry, I am confused. It looks like there is no issue.

Is the trigger, when insert/update table B, table C will be inserted with rows,defined by yourself or generated by replication?

Also, table A is on publisher side, are table B and C on subscriber side? What's your replication scenario?

THanks

Yunjing

|||

the triggers are defined by myself for business purpose.

table A and table B exist in both publisher and subscriber. Our approach is whenever there is an update in table A and B in oracle publisher, the transaction replicate to table A and B in Mssql2005 subscriber and user trigger updates table C.

|||

stephanie, please be clear where and what the problem is. We understand now you're using transactional replication with Oracle publisher, correct? The triggers are user-defined at the subscriber, correct? If you drop the user triggers at the subscriber, does the insert proc executed by the distribution agent succeed? If so, the problem must be in your triggers. If the problem persists, then it looks like it has nothing to do with triggers. Have you tried running with profiler to see what values are being passed and what statements are being executed?

|||

I found the replication command with error in replication monitor and sp_browsereplcmds

I have traced though the triggers, the trigger checked the records in other tables which are also replicated from oracle.

And I found that the records are missing in other tables which required in the triggers...and cause the replication error.

Anyone can advise me how does the replication command apply to subscriber? The command with xact_seqno(24EC and command_id:27) causing error and the command with xact_seqno(24E7 and command_id:13) doesn't appear in the table...

How to determine to sequence of commands applying to subscriber? Thanks in advance!

|||also, if I manual insert the record into the table by sql or calling the replication sp sp_MSins, the trigger works fine. Guessing it may be some problem in sequence of command or commit replication transactions. Any idea? Thanks in advance!

Replication Error

I found a problem in replication which we have 3 tables, namely tab A, tab B and tab C

replication will apply on tab A and tab B

and there is a trigger on tab A and tab B, whenever insert/update on tab A it fires trigger to update tab b

whenever insert/update on tab B it fires trigger to update tab C

And I found the replication error from tab A on updating tab C. If I manually insert the row, it works fine.....

Any advise? Thanks in advance!

what's the error?|||

Error Code 515:

Cannot insert the value NULL into column 'amount_id', table 'dev.dbo.tab_c'; column does not allow nulls. INSERT fails.

Thanks

|||

Can you also insert value NULL successfully into column 'amount_id" of table_C manually?

-Yunjing

|||

No, actually, the column 'amount_id' is defined as 'not null'. While inserting the row into tab A, it fires the trigger and check the conditions in tab b, and then insert the row into tab c. However, I found the 'amount_id' is defined in the trigger and shouldn't be null.

I used sp_browsereplcmds to find out the command with error and manual exec the store proc.

sp_MSins_ADMTAB_A with the field values and it works. After the row inserted, the pending transactions delivered to the subscriber successfully (as I set the replication option to skip the error 2627 for duplicate primary key)

|||

Sorry, I am confused. It looks like there is no issue.

Is the trigger, when insert/update table B, table C will be inserted with rows,defined by yourself or generated by replication?

Also, table A is on publisher side, are table B and C on subscriber side? What's your replication scenario?

THanks

Yunjing

|||

the triggers are defined by myself for business purpose.

table A and table B exist in both publisher and subscriber. Our approach is whenever there is an update in table A and B in oracle publisher, the transaction replicate to table A and B in Mssql2005 subscriber and user trigger updates table C.

|||

stephanie, please be clear where and what the problem is. We understand now you're using transactional replication with Oracle publisher, correct? The triggers are user-defined at the subscriber, correct? If you drop the user triggers at the subscriber, does the insert proc executed by the distribution agent succeed? If so, the problem must be in your triggers. If the problem persists, then it looks like it has nothing to do with triggers. Have you tried running with profiler to see what values are being passed and what statements are being executed?

|||

I found the replication command with error in replication monitor and sp_browsereplcmds

I have traced though the triggers, the trigger checked the records in other tables which are also replicated from oracle.

And I found that the records are missing in other tables which required in the triggers...and cause the replication error.

Anyone can advise me how does the replication command apply to subscriber? The command with xact_seqno(24EC and command_id:27) causing error and the command with xact_seqno(24E7 and command_id:13) doesn't appear in the table...

How to determine to sequence of commands applying to subscriber? Thanks in advance!

|||also, if I manual insert the record into the table by sql or calling the replication sp sp_MSins, the trigger works fine. Guessing it may be some problem in sequence of command or commit replication transactions. Any idea? Thanks in advance!sql

Replication Details

Hi,

I used my DB and some tables for replication earlier, now i removed my all replication subscription and publication and my DB is out of replication.

Now i am altering my table for PK then its giving err as follows:

Cannot alter the table 'mstparty' because it is being published for replication.

From where i can find details, i mean in which sys table all replication obj are stored.

There is no Replication now on DB then why still table 'mstparty' has a replication err when i alter table.

Please advice as i am not able to alter my table or tables which earlier i used in replication and now i removed replication.Check this...
http://msdn2.microsoft.com/en-us/library/ms152757.aspx (http://msdn2.microsoft.com/en-us/library/ms152757.aspx)|||Run this query in your Distribution database. & see what data are you getting..?

Select * from MSpublications
Select * from MSarticles

If you are getting any data related your database, means your DB is still there for replication.

Use Publication Wizard from Enterprise Manager for remove publication.|||Not able to find out anything, as there is no subscription or publication exist at all.|||Can you post error along with error number..?|||here is the solutions below:

1. EXEC sp_removedbreplication 'your_database_name'

2. Execute the following procedure on the problematic database and pass the table name as the parameter:

EXEC sp_msunmarkreplinfo 'your_table_name'

3. You may not need this method, but take this as a last resort.

EXEC sp_configure 'allow',1
go
reconfigure with override
go
use your_database_name
go
update sysobjects set replinfo = 0 where name = 'your_table_name'
go
EXEC sp_configure 'allow',0
go
reconfigure with override
gosql

replication conflicts for 2 tables

Hi,
we are using merge replication between remote sites and
our central office. couple months ago we had a situation
where we had to insert some records and update other
records with these inserted records and then delete the
inserted records. Then we reinserted these records again
without replicating the deletes to our remote sites.
by doing this we had lots of conflicts.
I mannually deleted replicated and reinserted the records
again.
all other sites are fine but 2 of our sites, which were
disconnected during the delete replication did not get the
deleted records and they still shows conflicts every day
when they replicate. even though these records are not
being edited at all. For some reason they get marked for
replication and shows up in conflicts.
we don't care if those changes doesn't get replicated to
the remote sites becos they don't need those changes. how
do I stop them to show up in conflicts.
thanks
Kiran
did you resolve these conflicts using the conflict viewer? This is the
preferred way of solving this problem?
"Kiran" <anonymous@.discussions.microsoft.com> wrote in message
news:16bc201c41752$0defc130$a101280a@.phx.gbl...
> Hi,
> we are using merge replication between remote sites and
> our central office. couple months ago we had a situation
> where we had to insert some records and update other
> records with these inserted records and then delete the
> inserted records. Then we reinserted these records again
> without replicating the deletes to our remote sites.
> by doing this we had lots of conflicts.
> I mannually deleted replicated and reinserted the records
> again.
> all other sites are fine but 2 of our sites, which were
> disconnected during the delete replication did not get the
> deleted records and they still shows conflicts every day
> when they replicate. even though these records are not
> being edited at all. For some reason they get marked for
> replication and shows up in conflicts.
> we don't care if those changes doesn't get replicated to
> the remote sites becos they don't need those changes. how
> do I stop them to show up in conflicts.
> thanks
> Kiran
sql

Replication conflict tables

Greetings!
We have been running transactional replication environment in development and QA test. The other evening in a "emergency", development requested several table changes to many of the published tables. I was out of the office and with no laptop available,
I tried to blindly guide a coworker through the process of reestablishing the articles and the subscription (not entirely sure of what he had removed). Apparently, we erred and he published and subscribed everything, but now we have a conflict_ table fo
r every single table in the publication. None of the tables have any rows. The published and subscriber database are both on the same server (as is the distribution database).
I can remove the conflict tables for the subscriber database, but they also exist in the published database as system tables which can't be dropped. I haven't run across an sp that can remove these and am thinking I won't be able to short of rebuilding t
he database. Might've SQL Server gotten the idea that this was to be merge replication? That seems like the only reason I got these. Is there any clean way to remove these conflict tables without rebuilding the database?
Thanks much in advance!
Steve
It sounds like he created a merge publication and then deleted it. You can
safely drop these conflict tables (as long as you aren't running any merge,
immediate updating or queued updating subscribers) by runing the following
command in QA
select 'drop table '+name from sysobjects where name like 'conflict_%'
Then in your results pane select the results and then paste it back in the
Query pane, and exectue it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Steve H" <shoerle@.charter.net> wrote in message
news:19042C30-8B0A-41D3-AD44-4DE62725C3C2@.microsoft.com...
> Greetings!
> We have been running transactional replication environment in development
and QA test. The other evening in a "emergency", development requested
several table changes to many of the published tables. I was out of the
office and with no laptop available, I tried to blindly guide a coworker
through the process of reestablishing the articles and the subscription (not
entirely sure of what he had removed). Apparently, we erred and he
published and subscribed everything, but now we have a conflict_ table for
every single table in the publication. None of the tables have any rows.
The published and subscriber database are both on the same server (as is the
distribution database).
> I can remove the conflict tables for the subscriber database, but they
also exist in the published database as system tables which can't be
dropped. I haven't run across an sp that can remove these and am thinking I
won't be able to short of rebuilding the database. Might've SQL Server
gotten the idea that this was to be merge replication? That seems like the
only reason I got these. Is there any clean way to remove these conflict
tables without rebuilding the database?
> Thanks much in advance!
> Steve

Replication and User Defined Trigger

Hi, all:
We have 5 databases which contains invoice and invoiceHistory tables.
We have an update and insert trigger on invoice table to record every
modification into InvoiceHistory table. The invoiceHistory table is not
read only, it has some fields that the end user can edit (comments,
date ...etc). At the same time, we using scheduled snapshots every 5
minutes to 'refresh' the table at the suscribers. The problem is when
the replicate server replicate table invoice to a subscribe, the
trigger on invoice table will be triggered and update/insert
InvoiceHistory table in the subscribe. Then when the replicate server
replicate table InvoiceHistory, we will get duplicate record in
InvoiceTable, one is from Invoice table trigger and another is from
InvoiceHistory replicate.
If we do not replicate InvoiceHistory table, then those fields that end
user updated can not be sync to subscribes.
Can I disable the trigger on invoice table when replication?
Does anybody there have a better idea how to do something like this?
ThanksCheck for the NOT FOR REPLICATION option. If you put it, trigger will not be
fired for replication.
MC
<rockdale.green@.gmail.com> wrote in message
news:1143418413.367012.182670@.v46g2000cwv.googlegroups.com...
> Hi, all:
> We have 5 databases which contains invoice and invoiceHistory tables.
> We have an update and insert trigger on invoice table to record every
> modification into InvoiceHistory table. The invoiceHistory table is not
> read only, it has some fields that the end user can edit (comments,
> date ...etc). At the same time, we using scheduled snapshots every 5
> minutes to 'refresh' the table at the suscribers. The problem is when
> the replicate server replicate table invoice to a subscribe, the
> trigger on invoice table will be triggered and update/insert
> InvoiceHistory table in the subscribe. Then when the replicate server
> replicate table InvoiceHistory, we will get duplicate record in
> InvoiceTable, one is from Invoice table trigger and another is from
> InvoiceHistory replicate.
>
> If we do not replicate InvoiceHistory table, then those fields that end
> user updated can not be sync to subscribes.
> Can I disable the trigger on invoice table when replication?
> Does anybody there have a better idea how to do something like this?
>
> Thanks
>

Replication and User Defined Trigger

Hi, all:
We have 5 databases which contains invoice and invoiceHistory tables.
We have an update and insert trigger on invoice table to record every
modification into InvoiceHistory table. The invoiceHistory table is not
read only, it has some fields that the end user can edit (comments,
date ...etc). At the same time, we using scheduled snapshots every 5
minutes to 'refresh' the table at the suscribers. The problem is when
the replicate server replicate table invoice to a subscribe, the
trigger on invoice table will be triggered and update/insert
InvoiceHistory table in the subscribe. Then when the replicate server
replicate table InvoiceHistory, we will get duplicate record in
InvoiceTable, one is from Invoice table trigger and another is from
InvoiceHistory replicate.
If we do not replicate InvoiceHistory table, then those fields that end
user updated can not be sync to subscribes.
Can I disable the trigger on invoice table when replication?
Does anybody there have a better idea how to do something like this?
Thanks
Check for the NOT FOR REPLICATION option. If you put it, trigger will not be
fired for replication.
MC
<rockdale.green@.gmail.com> wrote in message
news:1143418413.367012.182670@.v46g2000cwv.googlegr oups.com...
> Hi, all:
> We have 5 databases which contains invoice and invoiceHistory tables.
> We have an update and insert trigger on invoice table to record every
> modification into InvoiceHistory table. The invoiceHistory table is not
> read only, it has some fields that the end user can edit (comments,
> date ...etc). At the same time, we using scheduled snapshots every 5
> minutes to 'refresh' the table at the suscribers. The problem is when
> the replicate server replicate table invoice to a subscribe, the
> trigger on invoice table will be triggered and update/insert
> InvoiceHistory table in the subscribe. Then when the replicate server
> replicate table InvoiceHistory, we will get duplicate record in
> InvoiceTable, one is from Invoice table trigger and another is from
> InvoiceHistory replicate.
>
> If we do not replicate InvoiceHistory table, then those fields that end
> user updated can not be sync to subscribes.
> Can I disable the trigger on invoice table when replication?
> Does anybody there have a better idea how to do something like this?
>
> Thanks
>

Replication and User Defined Trigger

Hi, all:
We have 5 databases which contains invoice and invoiceHistory tables.
We have an update and insert trigger on invoice table to record every
modification into InvoiceHistory table. The invoiceHistory table is not
read only, it has some fields that the end user can edit (comments,
date ...etc). At the same time, we using scheduled snapshots every 5
minutes to 'refresh' the table at the suscribers. The problem is when
the replicate server replicate table invoice to a subscribe, the
trigger on invoice table will be triggered and update/insert
InvoiceHistory table in the subscribe. Then when the replicate server
replicate table InvoiceHistory, we will get duplicate record in
InvoiceTable, one is from Invoice table trigger and another is from
InvoiceHistory replicate.
If we do not replicate InvoiceHistory table, then those fields that end
user updated can not be sync to subscribes.
Can I disable the trigger on invoice table when replication?
Does anybody there have a better idea how to do something like this?
ThanksCheck for the NOT FOR REPLICATION option. If you put it, trigger will not be
fired for replication.
MC
<rockdale.green@.gmail.com> wrote in message
news:1143418413.367012.182670@.v46g2000cwv.googlegroups.com...
> Hi, all:
> We have 5 databases which contains invoice and invoiceHistory tables.
> We have an update and insert trigger on invoice table to record every
> modification into InvoiceHistory table. The invoiceHistory table is not
> read only, it has some fields that the end user can edit (comments,
> date ...etc). At the same time, we using scheduled snapshots every 5
> minutes to 'refresh' the table at the suscribers. The problem is when
> the replicate server replicate table invoice to a subscribe, the
> trigger on invoice table will be triggered and update/insert
> InvoiceHistory table in the subscribe. Then when the replicate server
> replicate table InvoiceHistory, we will get duplicate record in
> InvoiceTable, one is from Invoice table trigger and another is from
> InvoiceHistory replicate.
>
> If we do not replicate InvoiceHistory table, then those fields that end
> user updated can not be sync to subscribes.
> Can I disable the trigger on invoice table when replication?
> Does anybody there have a better idea how to do something like this?
>
> Thanks
>

Replication and uniqueidentifier

Hope someone can help with this.
I have one database where all the tables were joined by a auto incrementing
column.
Now we are trying to see if we can move to having multiple databases
(replication) across different offices which has the same tables. Each office
would merge in their records but can see other offices records as well and
possibly make updates to it. We would try to implement two way merging.
We are coming to the realization that we can't use the autoincrementing id
and now possibly join all the tables using a unique identifier. We can't use
the auto id since we have multiple sql servers now and conflict could occur.
Two questions:
1. Is joining by unique identifier good
2. Can we implement merge replication using this unique identifier as I read
that sql server adds its own unique identifier column.
Any help would be appreciated.
Abdul Rauf
In general avoid guids when possible. Check out this link for a discussion
of the reasons why.
http://www.aspfaq.com/show.asp?id=2504
Basically to avoid primary key collisions you need to ensure that the data
which is entered in one database will never have the same primary key value
as data which is entered in another database.
What you really need to do is partitioning. You can use different identity
seeds to achieve this please check out
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80
HTH
"Abdul Rauf" <AbdulRauf@.discussions.microsoft.com> wrote in message
news:3F3DAC60-B9DE-446C-BF8C-12CF139A106B@.microsoft.com...
> Hope someone can help with this.
> I have one database where all the tables were joined by a auto
incrementing
> column.
> Now we are trying to see if we can move to having multiple databases
> (replication) across different offices which has the same tables. Each
office
> would merge in their records but can see other offices records as well and
> possibly make updates to it. We would try to implement two way merging.
> We are coming to the realization that we can't use the autoincrementing id
> and now possibly join all the tables using a unique identifier. We can't
use
> the auto id since we have multiple sql servers now and conflict could
occur.
> Two questions:
> 1. Is joining by unique identifier good
> 2. Can we implement merge replication using this unique identifier as I
read
> that sql server adds its own unique identifier column.
> Any help would be appreciated.
> Abdul Rauf

Replication and Timestamp

Hi,
I have a database that has tables with Timestamp field. I am trying to do a
transactional replication on this db. The wizard changed my "Subscription"
table's timestamp field to Binary format.
Now, the problem is that a report application (we didn't write it) require
this TimeStamp field as Timestamp datatype for it to work. We create the
replication mainly because of this application (we don't want it to take up
any real cpu cycle on the live server). Switching this field back to
timestamp breaks the replication.
Help...
thanks,
Alex
Hi Alex,
You may want to consider using merge replication or
transactional replication with the queued updating
option. For these replications, when articles contain a
timestamp column, the timestamp column is replicated,
but the literal timestamp values are not. The timestamp
values are regenerated when applying the initial
snapshot rows at the Subscriber. This allows timestamp
to continue using optimistic concurrency control (a
frequent usage). For snapshot and transactional
publications, and publications that allow immediate
updating, the literal values for a timestamp column are
replicated, but the data type for the replicated values
is changed to binary (8) on the Subscriber.
This information can be found at the "Data Needs and
Characteristics" topic in BOL:
http://msdn.microsoft.com/library/en...lsql/replplan_
5jub.asp
If you have any further questions, please feel free to
let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>Subject: Replication and Timestamp
>Date: Thu, 9 Dec 2004 16:20:43 -0800
>Lines: 19
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57801
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Hi,
>I have a database that has tables with Timestamp field.
I am trying to do a
>transactional replication on this db. The wizard
changed my "Subscription"
>table's timestamp field to Binary format.
>Now, the problem is that a report application (we
didn't write it) require
>this TimeStamp field as Timestamp datatype for it to
work. We create the
>replication mainly because of this application (we
don't want it to take up
>any real cpu cycle on the live server). Switching this
field back to
>timestamp breaks the replication.
>Help...
>thanks,
>Alex
>
>
|||Well, it works to a point...
Here is the problem I am faced with using this new method (Queued Update
setup).
1) Snapshot works fine.
2) When Transactional Replication happens, it will error out with "Syntax
Error/Access Denied Error".
3) Error happens because the Replication Wizard created a bunch of SPs on
the subscriber. And all these SPs contain space " ", "," and "$" in its
name. Main reason is that my Table names where these SPs based on contain "
", "," and "$".
4) Before switching to Queued Update method, I have a Tab named "Command"
under the Article setup screen. Now it is gone.
If there is a way for me to change the SPs name and tell the server to use
them, I am set. Or if there is a way for me to disable all these SPs, I
will be set too...
Please Help.
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> You may want to consider using merge replication or
> transactional replication with the queued updating
> option. For these replications, when articles contain a
> timestamp column, the timestamp column is replicated,
> but the literal timestamp values are not. The timestamp
> values are regenerated when applying the initial
> snapshot rows at the Subscriber. This allows timestamp
> to continue using optimistic concurrency control (a
> frequent usage). For snapshot and transactional
> publications, and publications that allow immediate
> updating, the literal values for a timestamp column are
> replicated, but the data type for the replicated values
> is changed to binary (8) on the Subscriber.
> This information can be found at the "Data Needs and
> Characteristics" topic in BOL:
> http://msdn.microsoft.com/library/en...lsql/replplan_
> 5jub.asp
> If you have any further questions, please feel free to
> let me know.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!tk2msftngp13.phx.gbl
> microsoft.public.sqlserver.replication:57801
> I am trying to do a
> changed my "Subscription"
> didn't write it) require
> work. We create the
> don't want it to take up
> field back to
>
|||Hi Alex,
A BUG has been filed for the type of problem you are
having with replication.
Q306608 BUG: Distribution Agent May Fail with Incorrect
Syntax
http://support.microsoft.com/?id=306608
The only workaround was to rename the tables without the
special characters.
The problem is that when Logreader generates the command
it does not use delimiters. There is no way to configure
it work differently. You may consider creating the
article differently. On the publication properties,
click the ... button and uncheck the "replace
insert/update/delete..." checkboxes to force the use of
straight SQL to deliver the commands. This is also
available with scripting as options on sp_addarticle
where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
perform slower but it should work. Please give this a
try and let me know how it works for you.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Fri, 10 Dec 2004 16:13:22 -0800
>Lines: 116
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP15.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57831
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Well, it works to a point...
>Here is the problem I am faced with using this new
method (Queued Update
>setup).
>1) Snapshot works fine.
>2) When Transactional Replication happens, it will
error out with "Syntax
>Error/Access Denied Error".
>3) Error happens because the Replication Wizard
created a bunch of SPs on
>the subscriber. And all these SPs contain space " ",
"," and "$" in its
>name. Main reason is that my Table names where these
SPs based on contain "
>", "," and "$".
>4) Before switching to Queued Update method, I have a
Tab named "Command"
>under the Article setup screen. Now it is gone.
>If there is a way for me to change the SPs name and
tell the server to use
>them, I am set. Or if there is a way for me to disable
all these SPs, I
>will be set too...
>Please Help.
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
a[vbcol=seagreen]
timestamp[vbcol=seagreen]
are[vbcol=seagreen]
values[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
field.[vbcol=seagreen]
this
>
>
|||William...
Thanks for the info... But unfortunately, I cannot change the Table Name at
the source. It is because the Source tables are from Navision (Another
Microsoft Product). And Navision uses Company Name + '$" to prefix the
table names.
Any chance for there is a hot fix for it?
Thanks,
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> A BUG has been filed for the type of problem you are
> having with replication.
>
> Q306608 BUG: Distribution Agent May Fail with Incorrect
> Syntax
> http://support.microsoft.com/?id=306608
>
> The only workaround was to rename the tables without the
> special characters.
> The problem is that when Logreader generates the command
> it does not use delimiters. There is no way to configure
> it work differently. You may consider creating the
> article differently. On the publication properties,
> click the ... button and uncheck the "replace
> insert/update/delete..." checkboxes to force the use of
> straight SQL to deliver the commands. This is also
> available with scripting as options on sp_addarticle
> where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
> perform slower but it should work. Please give this a
> try and let me know how it works for you.
>
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> <XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!TK2MSFTNGP15.phx.gbl
> microsoft.public.sqlserver.replication:57831
> method (Queued Update
> error out with "Syntax
> created a bunch of SPs on
> "," and "$" in its
> SPs based on contain "
> Tab named "Command"
> tell the server to use
> all these SPs, I
> wrote in message
> a
> timestamp
> are
> values
> http://msdn.microsoft.com/library/en...lsql/replplan_
> and
> V6.00.2900.2180
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> field.
> this
>
|||If there isn't a hotfix, as a work-around you might want to consider
transactionally replicating an indexed view of the table. If the subscriber
has to use the name as the tablename - ie with the hyphen, then a 'normal'
view on the subscriber could be used at that end.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Alex,
I'm sorry that I could not find other workarounds
regarding this issue, and there is not a hotfix for now.
However, I'm glad to tell you that this issue is planned
to be fixed in the next version of SQL Server. Currently
you may consider using Snapshot replication.
Feel free to let me know if I could explain anything
further.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
<OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
<nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Mon, 13 Dec 2004 10:41:13 -0800
>Lines: 223
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <uoTwTNU4EHA.2592@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57875
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>William...
>Thanks for the info... But unfortunately, I cannot
change the Table Name at
>the source. It is because the Source tables are from
Navision (Another
>Microsoft Product). And Navision uses Company Name +
'$" to prefix the
>table names.
>Any chance for there is a hot fix for it?
>Thanks,
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
Incorrect[vbcol=seagreen]
the[vbcol=seagreen]
command[vbcol=seagreen]
configure[vbcol=seagreen]
of[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
disable[vbcol=seagreen]
contain[vbcol=seagreen]
replicated,[vbcol=seagreen]
timestamp[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
to[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
via[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
>
>

replication and datetime columns

I have an interesting server occuring. We have transactional replication running with 1 pub and 6 subscribers. On nearly all the tables we have some sort of date column that's a smalldatetime. If I look at the pub the data will appear like:

2006-11-13 09:59:00

However, on all the subs it appears like:

2006-11-13 09:59:00.000

It's the same column and record but for some reason it's become a datetime. I checked the column types and they are both smalldatetime's.

Why is this happening? What can be done?

Thanks,

Phil

I am unable to repro this on my SQL 2000 and SQL 2005 servers. What version of SQL Server are you running and what SPs?|||

Actually I found the problem. It looks as if when you use the four part name server.db.dbo.tablename from the publisher that the column "appears" to be a datetime. When I actually go to the server and select it.. then it's the normal smalldatetime. I don't know if this has something to do w/ ODBC connection accross linked servers or what...

Thanks,

Phil

REplication and BLOB tables

Anyone ever see this error:
The process could not bulk copy into table '"JobApplBlob200501"'.
Expected the text length in data stream for bulk copy of text, ntext, or
image data.
(Source: ELMER (Data source); Error number: 4813)
Elmer is the Subscribing system.
The only odd thing I can see is the publisher and subscriber are build 922.
The distribution host server is build 818. I have other BLOB fields going
from the same publisher to the same subscriber through the same distributor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
Is this transactional replication ? Is this error during initial snapshot or
during intial load on the subscribers. I have included the replication group
'cos you have some experts in there like Hilary and Paul who can help
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:e20gvdqAFHA.2584@.TK2MSFTNGP09.phx.gbl...
> Anyone ever see this error:
>
> The process could not bulk copy into table '"JobApplBlob200501"'.
> Expected the text length in data stream for bulk copy of text, ntext, or
> image data.
> (Source: ELMER (Data source); Error number: 4813)
>
> Elmer is the Subscribing system.
> The only odd thing I can see is the publisher and subscriber are build
922.
> The distribution host server is build 818. I have other BLOB fields going
> from the same publisher to the same subscriber through the same
distributor.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
>

REplication and BLOB tables

Anyone ever see this error:
The process could not bulk copy into table '"JobApplBlob200501"'.
Expected the text length in data stream for bulk copy of text, ntext, or
image data.
(Source: ELMER (Data source); Error number: 4813)
Elmer is the Subscribing system.
The only odd thing I can see is the publisher and subscriber are build 922.
The distribution host server is build 818. I have other BLOB fields going
from the same publisher to the same subscriber through the same distributor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.orgIs this transactional replication ? Is this error during initial snapshot or
during intial load on the subscribers. I have included the replication group
'cos you have some experts in there like Hilary and Paul who can help
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:e20gvdqAFHA.2584@.TK2MSFTNGP09.phx.gbl...
> Anyone ever see this error:
>
> The process could not bulk copy into table '"JobApplBlob200501"'.
> Expected the text length in data stream for bulk copy of text, ntext, or
> image data.
> (Source: ELMER (Data source); Error number: 4813)
>
> Elmer is the Subscribing system.
> The only odd thing I can see is the publisher and subscriber are build
922.
> The distribution host server is build 818. I have other BLOB fields going
> from the same publisher to the same subscriber through the same
distributor.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
>

REplication and BLOB tables

Anyone ever see this error:
The process could not bulk copy into table '"JobApplBlob200501"'.
Expected the text length in data stream for bulk copy of text, ntext, or
image data.
(Source: ELMER (Data source); Error number: 4813)
Elmer is the Subscribing system.
The only odd thing I can see is the publisher and subscriber are build 922.
The distribution host server is build 818. I have other BLOB fields going
from the same publisher to the same subscriber through the same distributor.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.orgIs this transactional replication ? Is this error during initial snapshot or
during intial load on the subscribers. I have included the replication group
'cos you have some experts in there like Hilary and Paul who can help
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:e20gvdqAFHA.2584@.TK2MSFTNGP09.phx.gbl...
> Anyone ever see this error:
>
> The process could not bulk copy into table '"JobApplBlob200501"'.
> Expected the text length in data stream for bulk copy of text, ntext, or
> image data.
> (Source: ELMER (Data source); Error number: 4813)
>
> Elmer is the Subscribing system.
> The only odd thing I can see is the publisher and subscriber are build
922.
> The distribution host server is build 818. I have other BLOB fields going
> from the same publisher to the same subscriber through the same
distributor.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
>

Replication and BDE (Borland Database Engine)

Hi,
Is it true that BDE encounters problem when the database is used for
replication? We have problem with BDE when the tables are used in
publication and rowguid column is added to them. The error message returned
by BDE is not helpful at all (Capability is not supported!)
Any help would be greatly appreciated.
LeilaHi Leila
I believe ROWGUIDCOL is not supported by BDE (although I can't be certain),
but you should not have any need to retrieve/set this. If you do want them
returned try casting it to char/varchar.
John
"Leila" wrote:
> Hi,
> Is it true that BDE encounters problem when the database is used for
> replication? We have problem with BDE when the tables are used in
> publication and rowguid column is added to them. The error message returned
> by BDE is not helpful at all (Capability is not supported!)
> Any help would be greatly appreciated.
> Leila
>
>|||Thanks John,
It seems that BDE performs some queries that is not in your control (when
you work visually with database in Delphi IDE). These queries have problem.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...
> Hi Leila
> I believe ROWGUIDCOL is not supported by BDE (although I can't be
> certain),
> but you should not have any need to retrieve/set this. If you do want them
> returned try casting it to char/varchar.
> John
> "Leila" wrote:
>> Hi,
>> Is it true that BDE encounters problem when the database is used for
>> replication? We have problem with BDE when the tables are used in
>> publication and rowguid column is added to them. The error message
>> returned
>> by BDE is not helpful at all (Capability is not supported!)
>> Any help would be greatly appreciated.
>> Leila
>>|||Hi
Maybe it is time to switch to ADO?
John
"Leila" wrote:
> Thanks John,
> It seems that BDE performs some queries that is not in your control (when
> you work visually with database in Delphi IDE). These queries have problem.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...
> > Hi Leila
> >
> > I believe ROWGUIDCOL is not supported by BDE (although I can't be
> > certain),
> > but you should not have any need to retrieve/set this. If you do want them
> > returned try casting it to char/varchar.
> >
> > John
> >
> > "Leila" wrote:
> >
> >> Hi,
> >> Is it true that BDE encounters problem when the database is used for
> >> replication? We have problem with BDE when the tables are used in
> >> publication and rowguid column is added to them. The error message
> >> returned
> >> by BDE is not helpful at all (Capability is not supported!)
> >> Any help would be greatly appreciated.
> >> Leila
> >>
> >>
> >>
>
>

Replication and BDE (Borland Database Engine)

Hi,
Is it true that BDE encounters problem when the database is used for
replication? We have problem with BDE when the tables are used in
publication and rowguid column is added to them. The error message returned
by BDE is not helpful at all (Capability is not supported!)
Any help would be greatly appreciated.
Leila
Hi Leila
I believe ROWGUIDCOL is not supported by BDE (although I can't be certain),
but you should not have any need to retrieve/set this. If you do want them
returned try casting it to char/varchar.
John
"Leila" wrote:

> Hi,
> Is it true that BDE encounters problem when the database is used for
> replication? We have problem with BDE when the tables are used in
> publication and rowguid column is added to them. The error message returned
> by BDE is not helpful at all (Capability is not supported!)
> Any help would be greatly appreciated.
> Leila
>
>
|||Thanks John,
It seems that BDE performs some queries that is not in your control (when
you work visually with database in Delphi IDE). These queries have problem.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...[vbcol=seagreen]
> Hi Leila
> I believe ROWGUIDCOL is not supported by BDE (although I can't be
> certain),
> but you should not have any need to retrieve/set this. If you do want them
> returned try casting it to char/varchar.
> John
> "Leila" wrote:
|||Hi
Maybe it is time to switch to ADO?
John
"Leila" wrote:

> Thanks John,
> It seems that BDE performs some queries that is not in your control (when
> you work visually with database in Delphi IDE). These queries have problem.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...
>
>

Replication and BDE (Borland Database Engine)

Hi,
Is it true that BDE encounters problem when the database is used for
replication? We have problem with BDE when the tables are used in
publication and rowguid column is added to them. The error message returned
by BDE is not helpful at all (Capability is not supported!)
Any help would be greatly appreciated.
Leila
Hi Leila
I believe ROWGUIDCOL is not supported by BDE (although I can't be certain),
but you should not have any need to retrieve/set this. If you do want them
returned try casting it to char/varchar.
John
"Leila" wrote:

> Hi,
> Is it true that BDE encounters problem when the database is used for
> replication? We have problem with BDE when the tables are used in
> publication and rowguid column is added to them. The error message returned
> by BDE is not helpful at all (Capability is not supported!)
> Any help would be greatly appreciated.
> Leila
>
>
|||Thanks John,
It seems that BDE performs some queries that is not in your control (when
you work visually with database in Delphi IDE). These queries have problem.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...[vbcol=seagreen]
> Hi Leila
> I believe ROWGUIDCOL is not supported by BDE (although I can't be
> certain),
> but you should not have any need to retrieve/set this. If you do want them
> returned try casting it to char/varchar.
> John
> "Leila" wrote:
|||Hi
Maybe it is time to switch to ADO?
John
"Leila" wrote:

> Thanks John,
> It seems that BDE performs some queries that is not in your control (when
> you work visually with database in Delphi IDE). These queries have problem.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...
>
>

Replication and BDE (Borland Database Engine)

Hi,
Is it true that BDE encounters problem when the database is used for
replication? We have problem with BDE when the tables are used in
publication and rowguid column is added to them. The error message returned
by BDE is not helpful at all (Capability is not supported!)
Any help would be greatly appreciated.
LeilaHi Leila
I believe ROWGUIDCOL is not supported by BDE (although I can't be certain),
but you should not have any need to retrieve/set this. If you do want them
returned try casting it to char/varchar.
John
"Leila" wrote:

> Hi,
> Is it true that BDE encounters problem when the database is used for
> replication? We have problem with BDE when the tables are used in
> publication and rowguid column is added to them. The error message returne
d
> by BDE is not helpful at all (Capability is not supported!)
> Any help would be greatly appreciated.
> Leila
>
>|||Thanks John,
It seems that BDE performs some queries that is not in your control (when
you work visually with database in Delphi IDE). These queries have problem.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...[vbcol=seagreen]
> Hi Leila
> I believe ROWGUIDCOL is not supported by BDE (although I can't be
> certain),
> but you should not have any need to retrieve/set this. If you do want them
> returned try casting it to char/varchar.
> John
> "Leila" wrote:
>|||Hi
Maybe it is time to switch to ADO?
John
"Leila" wrote:

> Thanks John,
> It seems that BDE performs some queries that is not in your control (when
> you work visually with database in Delphi IDE). These queries have problem
.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:782B8B52-5D32-4913-8B8A-40FA8C78AAE2@.microsoft.com...
>
>

replication alternatives

Anyone know of third party tools that would do the same
thing? Maybe without alter replicated tables restriction?
TIA, ChrisR
Chris,
Datamirror is sometimes mentioned in this newsgroup. I suppose a solution
could also be based on datacompare.
The main alternative that comes up is of course DTS/log shipping. These
solutions are for different scenarios, but often fit the bill. Using DTS if
you have updating subscribers can be painful however to set up.
BTW, transactional/snapshot replication (standard) doesn't alter the schema.
HTH,
Paul Ibison