Gain a better understanding of how to develop your SQL Server Mobile applications to handle multi-user access and data synchronization with Microsoft SQL Server 2005.
2005-04-04
2,112 reads
Microsoft® SQL Server™ enables third-party products to become Publishers within the SQL Server replication framework. The Replication Distributor Interface allows replication from heterogeneous databases that provide 32-bit OLE DB drivers to Subscribers running SQL Server 2000. Heterogeneous data sources include:
* Oracle databases
* DB2 databases
* Microsoft Access databases
* Other databases that comply with SQL Server ODBC or OLE DB Subscriber requirements
2005-03-16
2,300 reads
When transactional replication is used for high availability purposes, such as if you want the applications to access the replicated server when the primary database server fails, one of the hurdles SQL Server database administrators face when configuring replication is tables with identity columns.
In this article, I am going to discuss how to customize the replication in order to make the subscription database look identical to the publishing database, so that when there is a failure in the primary server, it is simple to fail over to the subscription database.
2005-03-07
2,807 reads
2005-01-19
1,069 reads
SQL Server 2000 replication is usually simple and easy to setup and work with. However there are many restrictions to ensure this, one of which is the alteration of a column which is engaged in replication. Author Paul Ibison brings us two options for altering columns.
2008-01-14 (first published: 2005-01-19)
45,516 reads
SQL Server 2000 replication is a great feature, but it can cause some headaches at times. Since the use of identities is something many people take advantage of, learning to handle these in a replication scenario is critical. Author Paul Ibison has done extensive work with replication and brings us two techniques to help manage the ranges of values.
2005-01-13
12,794 reads
Transactional replication is a type of replication provided by SQL Server 2000 that allows data modifications to be propagated incrementally between servers in a distributed environment.
2005-01-07
3,834 reads
Learn how to achieve scalable, high-performance merge replication applications. (White Paper)
2004-12-15
1,751 reads
2004-12-01
1,387 reads
2004-11-24
1,270 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Comments posted to this topic are about the item The AI Bubble and the...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers