Ads
06 November 2014
19 October 2014
Replicated Transaction Information:Oldest distributed LSN OR The process could not execute 'sp_repldone/sp_replcounters'
Some times this is resolved by using repl_done command along with repl_flush.
This time we faced issue and went unsuccessful. Then we followed below steps.
1. Stopped Log Reader Agent
2. EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
3. sp_repleflush
4. Started Log reader agent
5. Replication came in Sync.
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
go
sp_repleflush
This time we faced issue and went unsuccessful. Then we followed below steps.
1. Stopped Log Reader Agent
2. EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
3. sp_repleflush
4. Started Log reader agent
5. Replication came in Sync.
05 September 2014
Enable Change Tracking - SQL Server 2008
Setup.
- First enable Change tracking. Here’s some sample T-SQL you can execute to start the process
ALTER DATABASE SAMPLEDB
SET CHANGE_TRACKING = ON
(CHANGE_RETENTION = 10 DAYS, AUTO_CLEANUP = ON);
GO
After it’s enabled and you want to check on which databases are affected, run this T-SQL
SELECT DB_NAME(database_id) [mydbname]
FROM SYS.CHANGE_TRACKING_DATABASES;
GO
To
enable change tracking on a specific table use a query like this:
ALTER
TABLE dbo.MYTABLENAME
ENABLE CHANGE_TRACKING
WITH (TRACK_COLUMNS_UPDATED = OFF);
ENABLE CHANGE_TRACKING
WITH (TRACK_COLUMNS_UPDATED = OFF);
GO
Now
to check the tables that have tracking enabled, you can get that list here:
SELECT
OBJECT_NAME(OBJECT_ID) [MYTABLENAME]
FROM SYS.CHANGE_TRACKING_TABLES;
FROM SYS.CHANGE_TRACKING_TABLES;
GO
No
changes are required to statements for insert or update statements that are
enabled with change_tracking.
To
find out what’s changed after enabled, you can run a query similar to the
following
SELECT
ct.ID, ct.SYS_CHANGE_OPERATION, c.[NAME]
FROM
CHANGETABLE(CHANGES dbo.MYTABLENAME, 0) ct
JOIN
dbo.MYTABLENAME c ON c.[ID] = ct.[ID];
GO
19 August 2014
Grant access to Report Builder
-
Start Report Manager.
-
Click Site Settings.
-
Click Security.
-
If a role assignment already exists for the user or group for which you want to configure Report Builder access, click Edit.
Otherwise, click New Role Assignment. In Group or user, enter a Windows domain user or group account in this format:\ . If you are using forms authentication or custom security, specify the user or group account in the format that is correct for your deployment.
-
Select System User, and then click OK.
-
Click Home.
-
Click the Folder Settings tab.
-
Click the Security tab.
-
If a role assignment already exists for the user or group for which you want to configure Report Builder access, click Edit.
Otherwise, click New Role Assignment. In Group or user, enter a Windows domain user or group account in this format:\ . If you are using forms authentication or custom security, specify the user or group account in the format that is correct for your deployment.
-
Select Report Builder, and then click Apply.
-
Repeat to create or modify role assignments for additional users or groups.
29 July 2014
SQL Server 2012 SP2 failure - Validation for setting 'FAILOVERCLUSTERGROUP' failed. Error message: The cluster group cannot be determined for the instance name 'DBSQLPW80PA''
Error :
Resolution :
01) 2014-07-26
22:41:02 Slp: Sco: Attempting to get directory information for path C:\Program
Files\Microsoft SQL Server\
(01) 2014-07-26
22:41:05 Slp: The failover instance name 'DBSQLPW80PA' does not exist.
(01) 2014-07-26
22:41:05 Slp: Validation for setting 'FAILOVERCLUSTERGROUP' failed. Error
message: The cluster group cannot be determined for the instance name
'DBS80pA'. This indicates there is a problem with the product registry
setting for ClusterName, with product discovery, or the cluster resources.
(01) 2014-07-26
22:41:05 Slp: Validation for setting 'FAILOVERCLUSTERNETWORKNAME' failed. Error
message: The SQL Server failover cluster instance name 'DBSQLPW80PA' could not
be found as a cluster resource.
(01) 2014-07-26
22:41:05 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction"
threw an exception during execution.
(01) 2014-07-26
22:41:05 Slp:
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The
cluster group cannot be determined for the instance name 'DBS80PA'. This
indicates there is a problem with the product registry setting for ClusterName,
with product discovery, or the cluster resources. --->
Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException: The
cluster group cannot be determined for the instance name 'DBS80PA'. This
indicates there is a problem with the product registry setting for ClusterName,
with product discovery, or the cluster resources.
Resolution :
SStep 1.
Failover
SQL Node A to Node B
2Step 2.
On
Node A, backup existing registry entry
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL11.DBSQL30A\Cluster”
3
SStep 3.
On
Node A, update existing registry entry
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL11.DBSQL30A\Cluster” to DBSQLPW80PA
4Step 4.
Reboot
Node A
SStep 5.
Apply
SQL 2012 SP2 and hotfix to on Node A
Subscribe to:
Posts (Atom)
-
ERROR: report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the o...
-
Error messages: · The process could not execute 'sp_repldone/sp_replcounters' on ' SCKNLSSI '. (Source:...
-
Error Message: Replication-Replication Distribution Subsystem: agent DBA\DBA-EPDW-EPDW-DB6C\DB6C-5 failed. The subscription(S) have been...