Friday, September 13, 2013

[SQL 2012] CDC; AlwaysOn and CDC Jobs question.

[SQL 2012] CDC; AlwaysOn and CDC Jobs question.

CDC; AlwaysOn and CDC Jobs question.

Posted: 13 Sep 2013 02:16 AM PDT

Hi all,I have a Primary Replica A and Secondary B part of the AG Group. CDC is enabled at the Primary and the CDC jobs are created by default when you enable(CDC) on the Primary.According to the Microsoft article [url=http://technet.microsoft.com/en-us/library/hh403414.aspx][/url] The best practice would be: [QUOTE]You should create the jobs at all of the possible failover targets before failover, and mark them as disabled until the availability replica at a host becomes the new primary replica. The CDC jobs running at the old primary database should be also disabled when the local database becomes a secondary database. To disable and enable jobs, use the @enabled option of sp_update_job (Transact-SQL). For more information about creating CDC jobs, see sys.sp_cdc_add_job (Transact-SQL).[/QUOTE]However, When I try to specifically run the sp_cdc_add_job for the Secondary it says the "Could not update the metadata for database 'DBName' to indicate that a Change Data Capture job has been added" Two questions:1) Should I script the Job out from ServerA and run it on B?2) Proposed Solution : (After I sucessfully recreate Jobs on both the replica's) At every Job execution step add this :If sys.fn_hadr_backup_is_preferred_replica( @dbname ) = 1 (Checks whether server is primary) BEGIN--RUN CDC JOB ENDELSE EXITDoes this make sense? Feedback/suggestions would be appreciated.

version_ghost_record_count

Posted: 12 Sep 2013 09:25 PM PDT

Hi,I understand that [version_ghost_record_count] as retrieved from sys.dm_db_index_physical_stats shows the ghost records count sustained by a snapshot isolation transaction in an allocation unit.My question is this:I am seeing version ghost records in one of my databases but the database has Snapshot Isolation switched off. Is this possible?

monitorLoop

Posted: 12 Sep 2013 09:23 PM PDT

Hello.In SQL SERVER 2012, the xml of the event class 137 has now a new attribute, monitorLoop="xxxxxx" in the tag blocked-process-report. "xxxxxx" is a sequential number that it can to be repeated.What is this? I don't find anything about that.Thanks.

Error 18059: Impersonation Contexts

Posted: 12 Sep 2013 05:25 AM PDT

We have an app (from Active Networks) which, since being upgraded and moving to SQL Server 2012, repeatedly throws this error multiple times through the day: Error: 18059, Severity: 20, State: 1.From what I've read, documentation points to this being a problem with application pooling and security impersonation. As far as I can tell (from a profiler trace), it seems like the app initiates a connection, assumes an application role, then a new connection is made with the same credentials which throws the error. But, I may be incorrect in my observations.Has anyone seen anything like this before? The vendor seems certain that we're an isolated case and they haven't seen the same problem anywhere else, but we're no further towards resolving the error.

SS 2012 Data Tools to Manage SS 2005?

Posted: 12 Sep 2013 04:50 AM PDT

I just installed the Sql Server 2012 Client and Data tools on a term server in the hopes that we could use them to manage our Sql Server 2005 servers. Mgt Studio seems to work well with those. However, using Sql Server 2012 Data Tools, will we able to1) modify existing 2005 SSIS packages and resave them to our 2005 Sql Servers (Integration Services)?2) create new SSIS packages and save them to our 2005 SQL Servers w/ Integration Services?Hopefully the answer is 'yes' to the above and, if so, if you have links on the right way to do this, let me know. For example, I am wondering if you have to upgrade all the packages, etc.
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog