Shouldn't I get a PUSH error ?

Shouldn't I get a PUSH error ?

Post by Lennart Nystro » Sat, 12 Jan 2002 23:13:19



     Hi !
  Scenario :
  - PULL 2 records from the SQL Server 2000 with TRACKING
    ON and error table specified.
  - Using the QA I make a change to one of the records
    at the SQL Server 2000.
  - Make changes to the records at the Pocket PC emulator.
  - Do a PUSH from the Pocket PC receive status OK
    no error message ?!  
   - Changes made at the Pocket PC emulator overrides
     the one earlier done at the SQL Server 2000 !

    Any idea ?
    Thanks
    Lennart N.

 
 
 

Shouldn't I get a PUSH error ?

Post by Brad Syputa - M » Sun, 13 Jan 2002 02:46:38


From the SQL CE Books On Line:

RDA tracked Pull and Push methods use optimistic concurrency control. SQL
Server does not keep pulled records locked. When the application calls Push,
the changes made to the local SQL Server CE database are unconditionally
applied to the SQL Server database. This may cause changes made by other
users of the SQL Server database to be lost.

Brad

This posting is provided "AS IS" with no warranties, and confers no rights.


Quote:

>      Hi !
>   Scenario :
>   - PULL 2 records from the SQL Server 2000 with TRACKING
>     ON and error table specified.
>   - Using the QA I make a change to one of the records
>     at the SQL Server 2000.
>   - Make changes to the records at the Pocket PC emulator.
>   - Do a PUSH from the Pocket PC receive status OK
>     no error message ?!
>    - Changes made at the Pocket PC emulator overrides
>      the one earlier done at the SQL Server 2000 !

>     Any idea ?
>     Thanks
>     Lennart N.


 
 
 

Shouldn't I get a PUSH error ?

Post by Lennart Nystro » Tue, 15 Jan 2002 20:41:05


A follow up question (It seems like I don't fully
understand PUSH errors !) :
-  A user PULL a record.
-  Another user PULL the same record.
-  Both users do updates on different recordfields.
-  Then both users do a PUSH.
-  Will this create PUSH errors ?
    Regards,
    Lennart N.

Quote:>-----Original Message-----
>From the SQL CE Books On Line:

>RDA tracked Pull and Push methods use optimistic

concurrency control. SQL
Quote:>Server does not keep pulled records locked. When the

application calls Push,
Quote:>the changes made to the local SQL Server CE database are
unconditionally
>applied to the SQL Server database. This may cause

changes made by other
>users of the SQL Server database to be lost.

>Brad

>This posting is provided "AS IS" with no warranties, and
confers no rights.




>>      Hi !
>>   Scenario :
>>   - PULL 2 records from the SQL Server 2000 with
TRACKING
>>     ON and error table specified.
>>   - Using the QA I make a change to one of the records
>>     at the SQL Server 2000.
>>   - Make changes to the records at the Pocket PC
emulator.
>>   - Do a PUSH from the Pocket PC receive status OK
>>     no error message ?!
>>    - Changes made at the Pocket PC emulator overrides
>>      the one earlier done at the SQL Server 2000 !

>>     Any idea ?
>>     Thanks
>>     Lennart N.

>.

 
 
 

Shouldn't I get a PUSH error ?

Post by Brad Syputa - M » Wed, 16 Jan 2002 02:45:51


If both Push succeed, there will be no error. In a scenario with 2 users
Pushing data, and you expect the data to be over written, then you are
really looking for some type of Conflict resolution. There is no Conflict
resolution for Push. You will need to provide that logic ahead of time in
order to maintain your data. Using Identities and Unique ID's helps keep
data integrity and and correct.

If you do not want to provide the logic for Pull, please take a look at
Replication. With a little more overhead, Replication provides some logic to
help maintain your data.

Brad

This posting is provided "AS IS" with no warranties, and confers no rights.


> A follow up question (It seems like I don't fully
> understand PUSH errors !) :
> -  A user PULL a record.
> -  Another user PULL the same record.
> -  Both users do updates on different recordfields.
> -  Then both users do a PUSH.
> -  Will this create PUSH errors ?
>     Regards,
>     Lennart N.

> >-----Original Message-----
> >From the SQL CE Books On Line:

> >RDA tracked Pull and Push methods use optimistic
> concurrency control. SQL
> >Server does not keep pulled records locked. When the
> application calls Push,
> >the changes made to the local SQL Server CE database are
> unconditionally
> >applied to the SQL Server database. This may cause
> changes made by other
> >users of the SQL Server database to be lost.

> >Brad

> >This posting is provided "AS IS" with no warranties, and
> confers no rights.




> >>      Hi !
> >>   Scenario :
> >>   - PULL 2 records from the SQL Server 2000 with
> TRACKING
> >>     ON and error table specified.
> >>   - Using the QA I make a change to one of the records
> >>     at the SQL Server 2000.
> >>   - Make changes to the records at the Pocket PC
> emulator.
> >>   - Do a PUSH from the Pocket PC receive status OK
> >>     no error message ?!
> >>    - Changes made at the Pocket PC emulator overrides
> >>      the one earlier done at the SQL Server 2000 !

> >>     Any idea ?
> >>     Thanks
> >>     Lennart N.

> >.

 
 
 

1. Getting Help from someone that we Shouldn't have

I am relatively new to SQL so i have been trying to learn
things from people whom i thought knows more than I.  
this "so-called" db scialist was trying to move my Main db
from one drive to another by going into the properties of
the db and adding another db file and t-log file.  then he
tried going back in and deleteting this new location  for
each (db,tlog)(he decided this was not going to work) but
it would not delete the t-log since it was not empty. (I
should have stopped him there, but...) he opened the file
in notepad and deleted its contents and saved it. (&^%
$*&!!!) Now the db is greyed out and labeled (Suspect) (he
cussed and i cried) so he tried moving a copy of the
original tlog to the location he created but it gives and
error that there is something wrong with the new file
location. (more cussing and crying) So he gets the idea to
detach and re-attach the db in EM to reset the locations.
It detached but now it will not re-attach due to same
error.  Is there any help? (weeping...)

2. SELECT TOP @pagesize FROM [Companies]

3. Getting ObjectPal to 'push' another button

4. Keys? Contraints?

5. Error 3284 - Index already exists (it shouldn't apply)

6. Setting filters on tables

7. PUSH (with VC++) getting error : 28543

8. Backup to different server

9. PUSH (from a VC++ prg) getting error : 28543

10. Getting error while 'Synchronsing replication'

11. Getting 'Cannot resolve collation conflict..' error

12. Shouldn't large objects be MVCC-aware?

13. Why shouldn't I use Gupta?