WINS
Aug 3, 2006Does SQL 2005 require WINS?
View 1 Replies
ADVERTISEMENT
Dns/Wins & Tcp Sockets/named Pipes @ Sql 7
Sep 4, 2001We would like to use dns entries (CNAME) to create transparency between server infrastructure and logical servernames. So we could physically move databases onto another server and changing the dns entry without reconfiguring all client applications.
Old situation:
- Financeapplication connects to SERVERA (wins) through a .ini file.
New situation:
- Financeapplication connects to finserver.mydomain.be (CNAME)
- finserver.mydomain.be points to servera.mydomain.be (A record) in dns
- servera.mydomain.be is refering to the ip address of SERVERA
We tried to connect and got a 'get_overlapped_results' (clientside) when using a dns name in combination with named pipes. At the server we are getting this error:
Error: 17832, Severity: 18, State: 8
2001-08-24 13:10:16.64 ods Connection opened but invalid login packet(s) sent. Connection closed.
Connecting to the wins name of the server does work! Connecting to the dns name also works when using tcp sockets instead of named pipes.
Though, on some client pc's this does work with named pipes too, but we couldn't find any regularity or logic when it works or when it doesn't (service packs, mdac versions, NT/95/98/2000, ... etc).
We also noticed that integrated security works with tcp sockets when using dns names, but it doesn't when using wins names.
Does anyone have a clue?
Kurt.
Merge Replication Using Wins Mobile 5.0
May 3, 2006Hi all,
I have developed a mobile program with sql server 2000 merge replication. It works fine in Win mobile 2003 OS, but, not working at all after I upgrade the mobile OS to Win mobile version 5.0
Does anyone have any idea at all what's going on?
Thanks a lot.
AngelaC
Update Delete Wins Conflict (Type 3) Non Convergence Issue
Jan 26, 2007Topology:
Merge Replication (Using Web Sync anonymous pull subscriptions)
SQL 2005 SP1 all nodes
Scenarios:
I have two subscribers both have sync'd and data appears fine. Then one of the subscribers deletes a row whilst the other subscriber makes an update to the same row. The subscriber who deleted sync's first and the row has gone from the subscriber DB and the Publisher DB.
The second subscriber who still has the newly updated row in it's DB then sync's. There is a conflict of Type 3 (Update Delete Wins Conflict) which the conflict resolver states that the last subscriber to sync lost the conflict and the deleted row wins.
However this has caused problems. After sync has occurred the second subscriber still has the updated row in it's DB. The row does not exist on either the publisher or the subscriber where it was deleted. The data has become non-convergent.
I have used the Microsoft COM resolver Last Datetime wins and specified our [lud] datetime column. Now in my understanding in a type 3 situation the winning row (The deleted row) should be propogated to the publisher and subscriber and thus the data should have been removed at all nodes regardless of whether it had been updated or not.
Also to add another twist, the delete was performed before the update (Chronologically speaking) therefore I would assume the resolver should have taken the update to be the winning row (i.e. Type 4 Update Wins Delete Conflict) at least because a deleted row will have NULL in the [lud] column therefore the updated row with a NON NULL value for [lud] would be the winner.
Am I missing something here, or is the resolver not performing as described in Books On-Line
Cheers
Rab