Is it normal to have these jobs running on SQl for Microsoft Crm?
We have been running Microsoft CRM 3.0 in production for 7 months now and we just
noticed that the following SQL jobs have been failing:
MSCRM.update contract states
MSCRM.ftcat_documentindex
MSCRM Identity Reseeding
MSCRM Index Defragmentation
MSCRM Index Reindexing
MSCRM Stored Procedure Priming
I think it is just because they have been pointing towards the wrong
database within SQL.
2 Questions:
1) Is it normal to have these jobs running on SQl for CRM?
2) Which database do I want these to point at? Metabase or MSCRM?
We use v1.2 and have recently configured a test environment here to evaluate
CRM 3.0. From what I see in our 3.0 installation, those SQL jobs are pointing
to the MSCRM database. Also, I beleive it is normal for those jobs to be
running on SQL for CRM. For example, the reindexing job is especially
important for databases such as the CRM DB. Looking at our Index Reindexing
job, it looks like by default it will run once a week on Saturday at 12a.m.
Often these jobs fail due to a sescurity problem with the ID they are tied
to. You can modify the user context to SA or another account with
appropriate rights and that often solves the problem.