I would appreciate if someone could help me with the following problem: We use two SQL Server 2008 R2 databases under transactional replication: transactional publication with updatable subscriptions. because we run out of disk space we need to move the database files into a new drive. But I don’t want to break the replication. What I’m looking for are the required steps that will help me to move the files to the new drive. Thanks [...]Continue Reading »
Do I need to disable access to a publisher database when setting up SQL Server 2000 Transactional Replication?
I have a production database i.e. where there are constant updates and I’ve configured this to be published to another server using Transactional Replication. When I configure transactional replication I’ve been doing the following: disable access to the source database backup source DB then restore to subscription server configure replication re-enable DB access to our apps The problem with this approach is scheduling in downtime, having to suspend all the various timed scheduled tasks we [...]Continue Reading »
I recently upgraded my SQL 2005 server to SQL 2005 SP3. I have replication from SQL 2005 to SQL 2005 both are standard edition. During the upgrade I experienced no issues and the replication that was already setup continue to work great. I recently, tried to create a new publication for a new TEST account and I am getting the following error: “The concurrent snapshot for publication ‘TESTACCT’ is not available because it has not [...]Continue Reading »
I’ve got two SQL 2005 servers, one OLTP [let's call it SQLA] and one used for reporting [SQLB] to reduce load on SQLA when people run crazy queries. Our main database is replicated from SQLA to SQLB with transactional replication. The nature of the queries we run on SQLB are obviously very different, and therefore our index requirements are different too. Are there any issues with creating more indexes on SQLB, given that the database [...]Continue Reading »
After subscription had been marked for reinitialize, a new snapshot was generated. Log reader and queue reader agents are running. But when we try to turn on the synchronizing, we’re getting the following error: The concurrent snapshot for publication ‘DBName’ is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publication. [...]Continue Reading »
I’m planning to set up transactional replication for a 100Gb SQL Server 2008 database. I have the distributor and publisher on the same server, and am using push subscription. Should there be a performance impact on my publisher server when it creates the initial snapshot, and synchronises it with a subscriber? From what I’ve tried so far on a staging server, it seems to slow right down. Is there a better way to create the [...]Continue Reading »
When I’m adding one procedure article to the Publication the I get this error: The text data type cannot be selected as DISTINCT because it is not comparable the proc is a simple select distinct field1, field2, fieldn from tablex where id = @param1 The database is on compatibility level 80. The source server is SQL 2008 R2. Any help is appreciated. Thanks, Gabriel Guimarães I solved it, due to the sql 2000 compatibility (80) [...]Continue Reading »
- Understanding redundant power supplies
- Is there a way for administrators to disable users from installing Firefox extensions?
- Is there research material on NTP accuracy available?
- How to create a limited “domain admin” that does not have access to domain controllers?
- Can Windows RDC admin users be immune from being kicked?