Notifications
Announcements
No record found.
Hi
I've seen that with the BYOD option you can have it create clustered columnstore indexes. However, we are wondering if it is a supported scenario for us to create standard nonclustered indexes via a SQL interface (e.g. SSMS)?
Thanks,
Craig
Hi NotSoNewOzzie,
Do you mean you want to use SSMS to connect to your Azure SQL Database?
Quickstart: Use SSMS to connect to and query Azure SQL Database or Azure SQL Managed Instance:
docs.microsoft.com/.../connect-query-ssms
And check this document to create non-clustered index.
docs.microsoft.com/.../create-nonclustered-indexes
Thanks for the reply. I know how to connect to the Azure SQL DB.
What I'm asking is: If we create custom indexes on the BYOD database, is that allowed, and are there any concerns with us doing that?
Thanks
Hi Craig,
Can you tell how this question is related to Dynamics 365? You are asking about SQL features. As you mention BYOD, this database is in your own subscription and you own and maintain it.
Thanks.
With most vendors that push data into 3rd party databases, they have "rules" (Terms and conditions) about what you can and can't do. I am hoping to find out if creating custom indexes violates any terms of agreement of the Dynamics 365 BYOD feature.
There is no such document for this. BYOD is your own database, it just gets the data in D365FO and you can add indexes to it.
Sorry for non-answers to your question dude....
I was also looking for similar discussion on this topic in case someone actually knew your pain....from what I was told any schema changes in FnO will drop/re-create the table so any post-gens like rolling your own indexes would get wiped out so would have to be conscious of that. That said, the supported indexing in the BYOD sucks bad. I mean, who creates clustered columnstores on a giant varchar riddled table? Someone who doesn't want to keep working in their job that's who. Wait....its the same company who brought you CRM built by clustering on guids! Should we be surprised?
That said, it looks like unless you want to maintain your own indexes you're stuck with a terrible solution and that's BYOB. I did a quick test and pulling incremental change data out of the staged BYOB is 1,460X slower using clustered index than my own index. Yup. That's of course not even addressing the unfathomable fragmentation that the clustered columnstores will suffer from updates over time so that difference will just keep getting larger. If you have significant volume I'm guessing it'll eventually just tip over and your budget manager will call you one day and tell you the BYOB is eating up your entire Azure infrastructure budget. By more MSFT!
BTW....I suggest running your own clustered index defrags once a week.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 456 Super User 2025 Season 2
Martin Dráb 429 Most Valuable Professional
BillurSamdancioglu 239 Most Valuable Professional
