Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Replication / July 2008

Tip: Looking for answers? Try searching our database.

ThreadLast Post  Replies
Merge replication created w/ DMO - starting snapshot get error30 Jul 2008 19:33 GMT1
i am creating my merge publication via DMO in my VB.NET program. I used
to create only 1 publication, but since i now understand there is a
limit to the number of articles available for a single publication in
merge replication, i changed my program to make a publication for each
subscriber_type = local and Business Logic Handler30 Jul 2008 13:40 GMT2
I tried implementing a custom business logic handler in out replication
environment which consists out of a central publisher, three re-publishers
and a number of laptops as final subscribers.
In the UpdateHandler I check for updates on one table which are not
Precomputed Partitions30 Jul 2008 12:24 GMT3
We upgraded recently to SQL Server 2005 SP2 .
For some issues we are having, we are looking at precomputed partitiions
with our merge publication.
When I run a  sp_helpmergesubscription I see:
Bidirectional Transactional replication30 Jul 2008 12:16 GMT3
Do any one know where to get good Knowledge resources for writing and
implementing stored procedures for bidirectional transactional replication.
I f any body has one implemented recently can you spare the steps involved
and the best practises associated with this type of ...
merge replication sql 2005 64bit30 Jul 2008 12:13 GMT4
i was setting up merge replication and received a message that a table
couldn't be replicated because it has more than 254 columns. THe table
in question has 288 columns.
So  -  I can only replicate 254 columns?
issues with triggers in transaction replication30 Jul 2008 11:54 GMT1
I am making of sql 2005 - transaction replicaton.
data flows from the publisher to the subscriber - staging tables. From the
staging tables we want the data to move to the transaction tables at the
subscriber end.
Huge Replication Scenario29 Jul 2008 08:17 GMT2
We have several operational companies doing projects in the gas and oil
industry. These companies use a smorgasbord of applications running against a
central SQL Server in Central Europe.
To overcome latency issues we are planning to have about a dozen SQL Servers
merge replication conflict29 Jul 2008 05:48 GMT3
Hi SQL server expert,
I have a merge replication. The table has a primary key and an identity
column.
when I insert one row at the publisher and one row at the subscriber with
Which account on SQL 2005 web sync via https28 Jul 2008 15:07 GMT6
Hi, environment is SQL2005 [wkg_sql] non domain & IIS6 [wkg_iis] non
domain.
My steps are same as the steps in the following three articles:
How to: Configure a Publication to Allow for Web Synchronization (SQL
SQL Server 2005 : define a transactional replication where delete instructions are not replicated28 Jul 2008 10:27 GMT2
Did anyone perform a transactional replication where delete instructions
are not replicated ?
Advises would be very appreciate.
Regards
setting up Trans repl TO clustered servers28 Jul 2008 06:39 GMT1
I am settign up transactional replication from a single 2005 instance to a
clustered pair of 2005 sql servers. My question is do I set the connection to
hit the clustered virtual name or the actual server names in the cluster?
tia!
Transaction Replication26 Jul 2008 13:25 GMT1
I am using SQL2000, and want to set up the transaction replication.  Is is
ok to setup the simple mode on my publisher database?
Thanks,
Tomas
Merge Replication problem25 Jul 2008 10:03 GMT4
I have created a publisher on one SQL Server 2000 box for a merge
replication.  When I create the subscription, I receive the following error:
Message
The schema script '\\NVIS\$SQLDATA$xxxxxxx_1.sch' could not be propagated to
Guide for bakup/restore replicated DB24 Jul 2008 13:54 GMT2
I have implemented a system with 2 SQL 2000 servers with a DB for
archiving of production data of a manufacturing plant; the DB is merge
replicated between the 2 servers.
Now, the technical personnel of the plant has requested me a guide for
Merge Replication23 Jul 2008 17:03 GMT4
We have Server A, which is running Merge replication and acting as Publisher
and Distributor.
We have new server C which we needs to move our replication from A to this.
Server B is the only subscriber
Pages: 1 2 3 June, 2008
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.