hi all,
We currently encounter a big trouble:
We have set up a model of synchronization from PDA to SQL Server
succesfully. Everything is OK until SQL Server database met a trouble
and needed to restore database. We restored a rather old database (1
week ago) and then so many erros appeared. Database that is in PDA
contains much newer data than on SQL Server. When we synchorize, it
appeared error 28549: "The row update or insert cannot be reapplied due
to an integrity violation".
I would like to ask whether there is a standard process for Merge
Replication in case of restoring old database ?
FYI: SQL Server 2K with SP3.
Very appreciated for any help.
KNC
This will work if the retention period of the publication is longer than the
age of the backup.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"KNC" <khanh@.glassegg.com> wrote in message
news:1102943950.567639.151310@.z14g2000cwz.googlegr oups.com...
> hi all,
> We currently encounter a big trouble:
> We have set up a model of synchronization from PDA to SQL Server
> succesfully. Everything is OK until SQL Server database met a trouble
> and needed to restore database. We restored a rather old database (1
> week ago) and then so many erros appeared. Database that is in PDA
> contains much newer data than on SQL Server. When we synchorize, it
> appeared error 28549: "The row update or insert cannot be reapplied due
> to an integrity violation".
> I would like to ask whether there is a standard process for Merge
> Replication in case of restoring old database ?
> FYI: SQL Server 2K with SP3.
> Very appreciated for any help.
> KNC
>
|||hi Hilary,
You seems to misunderstand me, of course it still works. But it will
have trouble in following scenario:
- day 6, set up Merge Replication on SQL Server
- day 8, back up SQL Server database
- day 10, there is 1 new record 001 which is inserted into SQL
Server. Then it was synchronized with PDA, so PDA also contains this
new record 001.
- day 12, SQL Server database is corrupted, we restored from day 8.
Then record 001 is also inserted after database restored. When
synchronizing with PDA, it is conflicted with error 28549.
I would like to ask what is the standard process for Merge in case of
SQL server database is often restored.
Thanks much,
Khanh
Hilary Cotter wrote:
> This will work if the retention period of the publication is longer
than the[vbcol=seagreen]
> age of the backup.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "KNC" <khanh@.glassegg.com> wrote in message
> news:1102943950.567639.151310@.z14g2000cwz.googlegr oups.com...
trouble[vbcol=seagreen]
(1[vbcol=seagreen]
due[vbcol=seagreen]
Showing posts with label pda. Show all posts
Showing posts with label pda. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Merge replication UNIQUEIDENTIFIER Column?
Hi all,
I am using SQL 2005 sp1 to setup Merge replication for PDA access.
i created my Primary Key column a GUID using NEWID() as the default value.
When the snapshot was created it still went and added anothe GUID to all my
tables called rowguid.
i thought it was suposed to use the existing Unique GUID column before
creating a new one?
thanks for you advice. i hope i have the corect groups here?
inkquote:
If a published table does not have a uniqueidentifier column with the
ROWGUIDCOL property and a unique index, replication adds one
So, check for the rowguidcol property...
MC
"iKiLL" <iKill@.NotMyEmail.com> wrote in message
news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
> Hi all,
> I am using SQL 2005 sp1 to setup Merge replication for PDA access.
> i created my Primary Key column a GUID using NEWID() as the default value.
> When the snapshot was created it still went and added anothe GUID to all
> my tables called rowguid.
> i thought it was suposed to use the existing Unique GUID column before
> creating a new one?
> thanks for you advice. i hope i have the corect groups here?
> ink
>|||Sorry my point was that i had created one and SQL2005 still created its own.
Now from what i can tell i think i have figgerd it out.
The behaviour i was expecting was how SQL 2000 handled the row GUID column
for snapshots.
i am using SQL 2005.
it seems that there is in fact a property of the column called RowGuid that
must be set to Yes before creating the first snapshot.
Then SQL2005 will use that column instead of creating it's own. Just setting
the data type and making it the primary key is not enough.
Thanks for your input Marko.
"MC" <marko.culoNOSPAM@.gmail.com> wrote in message
news:eruu6p$pcf$1@.ss408.t-com.hr...
> quote:
> If a published table does not have a uniqueidentifier column with the
> ROWGUIDCOL property and a unique index, replication adds one
>
> So, check for the rowguidcol property...
>
> MC
>
> "iKiLL" <iKill@.NotMyEmail.com> wrote in message
> news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
>|||Yes, you need RowGuid property. Point is, you can have any number of
uniqueidentifiers in a table, but one of them needs to have this property
set. Since SQL Server doesnt want to guess which one would you like to have
as the 'main' GUID in a table, it adds another with rowguid property set.
Offcourse, if you allready have one it doesnt need to add it.
MC
"iKiLL" <iKill@.NotMyEmail.com> wrote in message
news:e2jo3%23bWHHA.600@.TK2MSFTNGP05.phx.gbl...
> Sorry my point was that i had created one and SQL2005 still created its
> own.
> Now from what i can tell i think i have figgerd it out.
> The behaviour i was expecting was how SQL 2000 handled the row GUID column
> for snapshots.
> i am using SQL 2005.
> it seems that there is in fact a property of the column called RowGuid
> that must be set to Yes before creating the first snapshot.
> Then SQL2005 will use that column instead of creating it's own. Just
> setting the data type and making it the primary key is not enough.
> Thanks for your input Marko.
>
>
>
> "MC" <marko.culoNOSPAM@.gmail.com> wrote in message
> news:eruu6p$pcf$1@.ss408.t-com.hr...
>
I am using SQL 2005 sp1 to setup Merge replication for PDA access.
i created my Primary Key column a GUID using NEWID() as the default value.
When the snapshot was created it still went and added anothe GUID to all my
tables called rowguid.
i thought it was suposed to use the existing Unique GUID column before
creating a new one?
thanks for you advice. i hope i have the corect groups here?
inkquote:
If a published table does not have a uniqueidentifier column with the
ROWGUIDCOL property and a unique index, replication adds one
So, check for the rowguidcol property...
MC
"iKiLL" <iKill@.NotMyEmail.com> wrote in message
news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
> Hi all,
> I am using SQL 2005 sp1 to setup Merge replication for PDA access.
> i created my Primary Key column a GUID using NEWID() as the default value.
> When the snapshot was created it still went and added anothe GUID to all
> my tables called rowguid.
> i thought it was suposed to use the existing Unique GUID column before
> creating a new one?
> thanks for you advice. i hope i have the corect groups here?
> ink
>|||Sorry my point was that i had created one and SQL2005 still created its own.
Now from what i can tell i think i have figgerd it out.
The behaviour i was expecting was how SQL 2000 handled the row GUID column
for snapshots.
i am using SQL 2005.
it seems that there is in fact a property of the column called RowGuid that
must be set to Yes before creating the first snapshot.
Then SQL2005 will use that column instead of creating it's own. Just setting
the data type and making it the primary key is not enough.
Thanks for your input Marko.
"MC" <marko.culoNOSPAM@.gmail.com> wrote in message
news:eruu6p$pcf$1@.ss408.t-com.hr...
> quote:
> If a published table does not have a uniqueidentifier column with the
> ROWGUIDCOL property and a unique index, replication adds one
>
> So, check for the rowguidcol property...
>
> MC
>
> "iKiLL" <iKill@.NotMyEmail.com> wrote in message
> news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
>|||Yes, you need RowGuid property. Point is, you can have any number of
uniqueidentifiers in a table, but one of them needs to have this property
set. Since SQL Server doesnt want to guess which one would you like to have
as the 'main' GUID in a table, it adds another with rowguid property set.
Offcourse, if you allready have one it doesnt need to add it.
MC
"iKiLL" <iKill@.NotMyEmail.com> wrote in message
news:e2jo3%23bWHHA.600@.TK2MSFTNGP05.phx.gbl...
> Sorry my point was that i had created one and SQL2005 still created its
> own.
> Now from what i can tell i think i have figgerd it out.
> The behaviour i was expecting was how SQL 2000 handled the row GUID column
> for snapshots.
> i am using SQL 2005.
> it seems that there is in fact a property of the column called RowGuid
> that must be set to Yes before creating the first snapshot.
> Then SQL2005 will use that column instead of creating it's own. Just
> setting the data type and making it the primary key is not enough.
> Thanks for your input Marko.
>
>
>
> "MC" <marko.culoNOSPAM@.gmail.com> wrote in message
> news:eruu6p$pcf$1@.ss408.t-com.hr...
>
Merge replication UNIQUEIDENTIFIER Column?
Hi all,
I am using SQL 2005 sp1 to setup Merge replication for PDA access.
i created my Primary Key column a GUID using NEWID() as the default value.
When the snapshot was created it still went and added anothe GUID to all my
tables called rowguid.
i thought it was suposed to use the existing Unique GUID column before
creating a new one?
thanks for you advice. i hope i have the corect groups here?
ink
Sorry my point was that i had created one and SQL2005 still created its own.
Now from what i can tell i think i have figgerd it out.
The behaviour i was expecting was how SQL 2000 handled the row GUID column
for snapshots.
i am using SQL 2005.
it seems that there is in fact a property of the column called RowGuid that
must be set to Yes before creating the first snapshot.
Then SQL2005 will use that column instead of creating it's own. Just setting
the data type and making it the primary key is not enough.
Thanks for your input Marko.
"MC" <marko.culoNOSPAM@.gmail.com> wrote in message
news:eruu6p$pcf$1@.ss408.t-com.hr...
> quote:
> If a published table does not have a uniqueidentifier column with the
> ROWGUIDCOL property and a unique index, replication adds one
>
> So, check for the rowguidcol property...
>
> MC
>
> "iKiLL" <iKill@.NotMyEmail.com> wrote in message
> news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
>
I am using SQL 2005 sp1 to setup Merge replication for PDA access.
i created my Primary Key column a GUID using NEWID() as the default value.
When the snapshot was created it still went and added anothe GUID to all my
tables called rowguid.
i thought it was suposed to use the existing Unique GUID column before
creating a new one?
thanks for you advice. i hope i have the corect groups here?
ink
Sorry my point was that i had created one and SQL2005 still created its own.
Now from what i can tell i think i have figgerd it out.
The behaviour i was expecting was how SQL 2000 handled the row GUID column
for snapshots.
i am using SQL 2005.
it seems that there is in fact a property of the column called RowGuid that
must be set to Yes before creating the first snapshot.
Then SQL2005 will use that column instead of creating it's own. Just setting
the data type and making it the primary key is not enough.
Thanks for your input Marko.
"MC" <marko.culoNOSPAM@.gmail.com> wrote in message
news:eruu6p$pcf$1@.ss408.t-com.hr...
> quote:
> If a published table does not have a uniqueidentifier column with the
> ROWGUIDCOL property and a unique index, replication adds one
>
> So, check for the rowguidcol property...
>
> MC
>
> "iKiLL" <iKill@.NotMyEmail.com> wrote in message
> news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
>
Monday, March 19, 2012
merge replication only need passwrd first time
Hello
I have an applicatiuon on a pda where i can synchronize the pda with
sql server 2000
When I start the application on open the synchronize window i have to
enter a user id and password.
repl.InternetLogin = userId
repl.InternetPassword = Password
I start the synchronization and it works.
The second time i synchronize it still works even with no password.
Why is that? I have to stop the application and start it again for it
to work.
If I enetr a wrong password when I synchronize the first time, I gett e
message saying: Authentication failed on the computer running IIS
I would like to get this message all the time when I synchronize with
an incorrect password.
What can I be doing wrong.
What form of authentication are you using on your IIS Server. Is it possible
that you have a blank password for the account userID?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<jensenove@.netscape.net> wrote in message
news:1144351127.584971.98050@.t31g2000cwb.googlegro ups.com...
> Hello
> I have an applicatiuon on a pda where i can synchronize the pda with
> sql server 2000
> When I start the application on open the synchronize window i have to
> enter a user id and password.
> repl.InternetLogin = userId
> repl.InternetPassword = Password
>
> I start the synchronization and it works.
> The second time i synchronize it still works even with no password.
> Why is that? I have to stop the application and start it again for it
> to work.
> If I enetr a wrong password when I synchronize the first time, I gett e
> message saying: Authentication failed on the computer running IIS
> I would like to get this message all the time when I synchronize with
> an incorrect password.
> What can I be doing wrong.
>
I have an applicatiuon on a pda where i can synchronize the pda with
sql server 2000
When I start the application on open the synchronize window i have to
enter a user id and password.
repl.InternetLogin = userId
repl.InternetPassword = Password
I start the synchronization and it works.
The second time i synchronize it still works even with no password.
Why is that? I have to stop the application and start it again for it
to work.
If I enetr a wrong password when I synchronize the first time, I gett e
message saying: Authentication failed on the computer running IIS
I would like to get this message all the time when I synchronize with
an incorrect password.
What can I be doing wrong.
What form of authentication are you using on your IIS Server. Is it possible
that you have a blank password for the account userID?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<jensenove@.netscape.net> wrote in message
news:1144351127.584971.98050@.t31g2000cwb.googlegro ups.com...
> Hello
> I have an applicatiuon on a pda where i can synchronize the pda with
> sql server 2000
> When I start the application on open the synchronize window i have to
> enter a user id and password.
> repl.InternetLogin = userId
> repl.InternetPassword = Password
>
> I start the synchronization and it works.
> The second time i synchronize it still works even with no password.
> Why is that? I have to stop the application and start it again for it
> to work.
> If I enetr a wrong password when I synchronize the first time, I gett e
> message saying: Authentication failed on the computer running IIS
> I would like to get this message all the time when I synchronize with
> an incorrect password.
> What can I be doing wrong.
>
Friday, March 9, 2012
Merge Replication IIS Worker Process Error
Everyday between 18:00 and 20:00 nearly 1000 PDA Subsriber anonymously
synchronise via Merge Replication and at least two time he have the error :
IIS Worker Process
Faulting application w3wp.exe, version 6.0.3790.1830,
faulting module sscerp20.dll, version 2.0.7331.0,
fault address 0x000110f4.
And subscriber which synchronising meanwhile becomes suspect.
Can someone offer a suggestion as to the cause of and correction for
this
error?
Thanks,
Hakan G
Here is some details about our system:
Client Side
OS: Windows Mobile 2003 4.21.1088
DB: SQL CE 2.0
Microsoft SQL Server CE (ssce20.dll) 2.00.4415.0
Microsoft SQL Server CE Client Agent (ssceca20.dll) 2.00.4415.0
Development Tools: VB.NET 2003
Service Pack: .NET Compact Framework 1.0 SP3
Server Side
OS: Microsoft 2003 SP1
Internet Information Services (INETINFO.EXE) 6.0.3790.1830
(srv03_sp1_rtm.050324-1447)
IIS Worker Process (w3wp.exe) 6.0.3790.1830 (srv03_sp1_rtm.050324-1447)
HW:IBM XSERIES_346 Intel(R) Xeon(TM) CPU 3.60GHZ (2CPU) 5,00 GB RAM DB:
SQL CE 2.0
DB:SQL Server Standart Edition 8.00.2039(SP4)
SQL CE Server 2.0
Microsoft SQL Server CE Server Agent (sscesa20.dll) 2.00.7331.0
Microsoft SQL Server CE Replication Provider (sscerp20.dll) 2.00.7331.0
Merge Replication Properties
--
status : 1
retention : 21
sync_mode : 1
allow_push : 1
allow_pull : 1
allow_anonymous : 1
centralized_conflicts : 1
priority : 100.0
snapshot_ready : 1
publication_type : 1
enabled_for_internet : 0
dynamic_filters : 1
has_subscription : 0
snapshot_in_defaultfolder : 1
alt_snapshot_folder : NULL
Merge Agent Profile:
parameter_name value
--
-BcpBatchSize 100000
-ChangesPerHistory 100
-DestThreads 4
-DownloadGenerationsPerBatch 500
-DownloadReadChangesPerBatch 500
-DownloadWriteChangesPerBatch 500
-FastRowCount 1
-HistoryVerboseLevel 1
-KeepAliveMessageInterval 300
-LoginTimeout 15
-MaxDownloadChanges 0
-MaxUploadChanges 0
-MetadataRetentionCleanup 1
-NumDeadlockRetries 5
-PollingInterval 60
-QueryTimeout 300
-SrcThreads 3
-StartQueueTimeout 300
-UploadGenerationsPerBatch 100
-UploadReadChangesPerBatch 100
-UploadWriteChangesPerBatch 100
-Validate 0
-ValidateInterval 60
You have a high-volumne replication scenario going on there and while I have not seen this specific error, I know you can increase the default thread pool used on the IIS server to broker all of this replication. There is a way to get -SrcThreads 3 to a larger number and I just saw it in the Books OnLine recently - I'll have a look and see if I can give you more details on this.
In the meantime perhaps Laxmi knows how to tune this setting off the top of his head.
-Darren
|||For configuring SQL Mobile Server Agent on IIS: Here are typical knobs,
1) MAX_THREADS_PER_POOL - No.of threads to handle the incoming sync requests
2) CLEANUP_INTERVAL - Sync sessions cleanup
3) USAGE - Restricting the support only to RDA/Merge/Both
Darren, Sorry I did not get what is meant by SrcThreads.
Thanks,
Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation
Subscribe to:
Posts (Atom)