Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Hi,We have two Dynamics CRM 365 v8.2.14 running on SQL Enterprise and Standard version.After update from 8.1.1 to 8.2.14 we have trouble with SQL script which is dropping indexex fron Enterprise version (KB2567984).If I run script on CRM Organization which is running on SQL Ent. I will received error:
Msg 1919, Level 16, State 1, Line 1Column 'AttributeMask' in table 'dbo.AuditBase' is of a type that is invalid for use as a key column in an index.First 2 are processed but 3rd one end with error.Any idea how to fix it?Thanks
Hope you are well.
Can you explain a bit more the scenario?
- What script are you trying to run?
- Why you are running it?
- You state first 2 are processed but 3rd one end with error. What are the first 2?
The difference on SQL version when it comes to auditing is that SQL standard does not support Partitioning but Enterprise does.
The specific error comes because AttributeMask is defined by default as nvarchar(max), which is invalid to be used as a key column in an index by design. In fact, if you use the SSMS UI to create an AuditBase index, Attributemask is not even presented to the user due to not being eligible:
Looking forward to your reply.
I already fix it.
This condition fixed issue. Problem was with size of index.
if (@recreateScript = 'DROP INDEX [dbo].[AuditBase].[ndx_ObjectId] CREATE NONCLUSTERED INDEX [ndx_ObjectId] ON [dbo].[AuditBase] (ObjectId ASC,ObjectTypeCode ASC,CreatedOn ASC,AuditId ASC,AttributeMask ASC)')
set @recreateScript = 'DROP INDEX [dbo].[AuditBase].[ndx_ObjectId] CREATE NONCLUSTERED INDEX [ndx_ObjectId] ON [dbo].[AuditBase] (ObjectId ASC,ObjectTypeCode ASC,CreatedOn ASC,AuditId ASC)'
Execute sp_executesql @recreateScript
Business Applications communities