replication

I want to be able to check the status of a publication and subscription in SQL Server 2008 T-SQL. I want to be able to determine if its okay, when was the last successful, sync, etc.. Is this possible? I know this is a little late.... SELECT (CASE WHEN mdh.runstatus = '1' THEN 'Start - '+cast(mdh.runstatus as varchar) WHEN mdh.runstatus = '2' THEN 'Succeed - '+cast(mdh.runstatus as varchar) WHEN mdh.runstatus = '3' THEN 'InProgress - '+cast(mdh.runstatus as varchar) WHEN mdh.runstatus = '4' THEN 'Idle - '+cast(mdh.runstatus as varchar) WHEN mdh.runstatus = '5' THEN 'Retry - '+cast(mdh

I have Solr running with multiple cores. Because of the heavy load, I want to set up a slave containing the exact same indexes. The documentation http://wiki.apache.org/solr/SolrReplication states "Add the replication request handler to solrconfig.xml for each core", but I only have one solrconfig.xml. My configuration: Config: /data/solr/web/solr/conf/config files Data: /data/solr/data/solr/core data dirs Is it really necessary to copy the solrconfig.xml for each core? And where should I put these multiple solrconfig files? solr.xml <?xml version="1.0" encoding="UTF-8" ?> <solr persistent=

Right now we are using PostgreSQL 8.3 (on Linux) as a database backend to our Ruby on Rails web application. Considering that on PostgreSQL database we actively use row level blocking and PL/PGSQL, what can we employ to secure our data -- I mean tools, packages, scripts, strategies -- to successfully replicate the database and build multi-master combination? I will appreciate master-slave suggestions as well. For example, if I put several application servers running Apache/Ruby to achieve higher performance and at the end deploy several database servers, is there any way to build multi-master

I am implementing the Hadoop Single Node Cluster on my machine by following Michael Noll's tutorial and have come across data replication error: Here's the full error message: > hadoop@laptop:~/hadoop$ bin/hadoop dfs -copyFromLocal > tmp/testfiles testfiles > > 12/05/04 16:18:41 WARN hdfs.DFSClient: DataStreamer Exception: > org.apache.hadoop.ipc.RemoteException: java.io.IOException: File > /user/hadoop/testfiles/testfiles/file1.txt could only be replicated to > 0 nodes, instead of 1 at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:1271) > at > org

As far as i know SQL Server provides 4 techniques for better availability. I think these are the primary usage scenarios, in summary :- 1) Replication would be primarily suited for online-offline data synchronization scenarios (laptop , mobile devices, remote servers). 2) Log shipping could be used to have a failover server with manual switching, whereas 3) Database Mirroring is an automatic failover technique 4) Failover Clustering is an advanced type of database mirroring. Am i right ? Thanks. Failover clustering is an availability technology that provides redundancy at the hardware level

I want to run an import of a large file into MySQL. However, I don't want it written to the binary log, because the import will take a long time, and cause the slaves to fall far behind. I would rather run it seperately on the slaves, after the fact, because it will be much easier on the system. The table in question is a new one, and therefore I don't really have to worry about it getting out of sync, as the master and all the slaves will have the same data in the end, because they will all import the same file eventually. I also don't want to change any of the replicate-ignore-* or binlog