Posts Tagged ‘MSSQL Server 2005’

Another snapshot agent for the subscription or subscriptions is running, or the server is working on a previous request by the same agent

11, Jun 2010

When creating publication in a merge replication in MSSQL Server 2005, especially for beginners, it’s not new that while doing it in SSMS, you run into steps that makes your publication incorrectly configured thus forcing you to abort the process. Now when you cancel the publication and you’re in the middle of generating the snapshot, [...]

Configuring distribution in an MSSQL Server 2005 cluster

2, Jun 2010

For some reason that you receive an error trying to configure distribution on your MSSQL Server 2005 cluster and it will ask you to use the actual server name when connecting to the server, verify that your server name in the sys.servers catalogue is the same as your instance name. To verify, while connected to [...]

Cannot manage or see shared drives/LUNs within MSSQL Server 2005 cluster

22, Apr 2010

This happens when the shared drives/LUNs in the cluster are not included in the dependency of your SQL Server resource. To fix this issue, go to SQL Server resource in the cluster’s SQL Group and go to properties. Under Dependency tab, modify it to include all the resources you wanted to be visible within your [...]

Cannot recreate publication: Invalid object name ‘dbo.sysmergepublications’ in MSSQL Server 2005 replication

5, Apr 2010

This happens when you delete subscription and publication directly from Replication node in SSMS tool. Run below against the database you deleted the replication before setting it up again. USE [database] EXEC sp_removedbreplication GO

The Distributor has not been installed correctly. [SQLSTATE 42000] (Error 20036)

1, Apr 2009

Once replication is setup, the “Expired subscription clean up” job on the distributor SQL Server fails with the above error. But replication functions normally, without any problems. When you have a dedicated SQL Server 2005 distribution server, that is not publishing any of its own databases, you are likely to get this error. Workaround To [...]

MSSQL: Restoring your database to a point in time

13, Mar 2009

If for some reason something happened to your database and you’d want to restore it to a point in time, you can do so by utilizing the transaction logs from your backup. Without the backup of transaction logs, you’re as good as being able to restore only to the last full backup. Below are the [...]


top