| Thread | Last Post | Replies |
|
| case sensitve master, case insensitive replica | 26 Feb 2010 19:00 GMT | 1 |
Is it possible to build a replica db case insensitive while the master is
case sensitive?
I have setup a replica database using collation CI , still the data is
handled as collation CS .
|
| Updatable subscription and Linked Servers. | 26 Feb 2010 17:00 GMT | 1 |
I just realized that when I sever the connection between the publisher and
describer, writes fail b/c it complains about not seeing the other server!!
Is this something that changes, does updatable subscription require 100%
uptime?
|
| Credentials for Mirroring | 24 Feb 2010 22:30 GMT | 1 |
We are mirroring a SQL Server 2008 Entreprise database over to another
SQLServer on another server. We had issues setting this up due to the
credentials the SQLServer service runs under (LocalSystem) seems it didn't
have permissions to write over to the target server. To solve ...
|
| Updatable subscription issue - Either no algorithm ... | 16 Feb 2010 17:43 GMT | 1 |
SQLException: Either no algorithm has been specified or the bitlength and
the algorithm specified for the key are not available in this installation of
Windows.
Replication was running fine and this morning all subscriptions were failing
|
| Peer2Peer. Dist to Sub 'Query timeout expired' | 14 Feb 2010 11:34 GMT | 2 |
Greetings all
I have P2P set up, SQL 2008 Ent, 2 peers, been working well for a month or 2.
After a recent large 'update' statement affecting 25k large records, data
hasn't made its way to the subscriber after some 10 hours. These records can
|
| REPOST - Agent message code 20084. The process could not connect to Subscriber | 10 Feb 2010 17:46 GMT | 1 |
All servers running SQL 2005
SQL server (NOLA) replicates to 35 remote locations (StoreXX).
Earlier this week, one publication started having problems connecting
to 30 of the 35 remote locations, with an error of:
|
| Transaction Replication Latency - millions of rows, days behind, only getting 3kbs throughput | 08 Feb 2010 21:49 GMT | 2 |
--Topology--
I've got a one way transactional push replication going over a 1mb WAN
to a datacenter in another state.
The Distributor is running on the Publisher box. The Publisher and the
|
| Agent message code 20084. The process could not connect to Subscriber | 04 Feb 2010 20:05 GMT | 1 |
All servers running SQL 2005
SQL server (NOLA) replicates to 35 remote locations (StoreXX).
Earlier this week, one publication started having problems connecting
to 30 of the 35 remote locations, with an error of:
|
| disable delete on transacional replication | 04 Feb 2010 17:22 GMT | 2 |
I have publisher and subscriber.
In one of my tables the new data is being added, and old data is being
deleted.
Is there a way on replication that it will only the insert and not the
|
| Field addition replication | 04 Feb 2010 16:57 GMT | 1 |
All servers are running SQL 2005.
I have several remote locations that replicate via transactional
replication to a central location (NOLA), the SQL server @ NOLA
replications to the corporate office (CORP).
|
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread